Downloaded 67 times
Uploaded byGordon Haff
How open source is driving DevOps innovation: CloudOpen NA 2015
The document discusses how open source principles drive innovation in DevOps by emphasizing automation, collaboration, and continuous integration and deployment workflows. It highlights the importance of culture in fostering trust and cooperation within organizations, as well as the role of various tools and governance models in supporting these practices. Open source not only contributes code but also provides guidance on leadership, transparency, and incentives that enhance DevOps efforts.
More Related Content
Similar to How open source is driving DevOps innovation: CloudOpen NA 2015
How open source is driving DevOps innovation: CloudOpen NA 2015
- 1. HOW OPEN SOURCEIS DRIVING DEVOPS INNOVATION Gordon Haff @ghaff William Henry @ipbabble Cloud & DevOps Product Strategy, Red Hat 17 August 2015
- 2. What is DevOps? Source:DevOps Days DC 2015 word cloud from Open Spaces.
- 3. DevOps applies opensource principles and practices with...
- 4. DEVOPS: THE WHAT &THE WHY TOOLS drawing from innovative development communities
- 5. A typical DevOpsworkflow
- 6. Tools for operations*/infrastucture Containerizedinfrastructure Orchestration Policy-based governance Configuration management Automation Packaging Updates * But they bleed into developer land!
- 7. Infrastructures evolve forcloud-native Monolithic app container Scale up by adding hardware resources Limited scale out through clustering Distributed, networked, containerized services Scale out by orchestrating services Faster iteration and release More robust RHEL APP APP SINGLE-HOST APPS MULTI-HOST APPS
- 8. Infrastructure layer: A CloudPlatform for Microservice Cloud Apps Provision apps from service catalog Orchestrate and place apps Run composed microservices in containers Provide dynamic, programmable infrastructure OPS MANAGEMENT AND SERVICE CATALOG (e.g. RED HAT CLOUDFORMS) CONTENT, ENTITLEMENT, AND LIFECYCLE (e.g. RED HAT SATELLITE) SERVICE SCHEDULER/ORCHESTRATOR (e.g. KUBERNETES) PaaS (e.g.OPENSHIFT) RED HAT ENTERPRISE LINUX OPENSTACK PLATFORM COMPUTE STORAGE NETWORK (e.g. OPENSTACK, CEPH, OPEN DAYLIGHT) RHEL ATOMIC HOST GUEST RHEL ATOMIC HOST GUEST Red Hat CloudForms Monitoring Docker Image Red Hat CloudForms Orchestration Docker Image Red Hat Satellite Content Docker Image Red Hat JBoss AMQ Docker Image App DB Docker Image Red Hat JBoss BRMS Docker Image
- 9. Tools for developer*workflows Collaboration CI/CD Issue tracking Source code control Code review Platform-as-a-Service * But they bleed into ops land!
- 10. CI/CD Pipeline Toolset CI/CDWorkflow UI
- 11. DEVOPS: THE WHAT &THE WHY Automation of PROCESS from development through ongoing operations
- 12. Automation as aCI/CD Process myRepo Project Repo CI Commit Push Pass/Fail Local Test Build Repo CD Release Repo Monitor Build Test Review/ Appr Deliver Deploy 3rd Party
- 13. myRepo Project Repo CI Commit Push Pass/Fail Local Test Build Repo CD Release Repo Monitor BuildTest Review/ Appr Deliver Deploy 3rd Party ● Collaboration ○ Kanban - Trello ○ Docs - etherpad, google docs ○ Pastebin - fpaste ○ Ticketing - Jira, Redmine ○ Coding - Eclipse, Emacs,
- 14. myRepo Project Repo CI Commit Push Pass/Fail Local Test Build Repo CD Release Repo Monitor BuildTest Review/ Appr Deliver Deploy 3rd Party ● Asset Management ○ Code/Config - git, subversion ○ Docs - git, Google docs ○ Policy/rules - ManageIQ, Katello
- 15. myRepo Project Repo CI Commit Push Pass/Fail Local Test Build Repo CD Release Repo Monitor BuildTest Review/ Appr Deliver Deploy 3rd Party ● Continuous Integration ○ Jenkins ○ Travis CI ○ BuildBot
- 16. myRepo Project Repo CI Commit Push Pass/Fail Local Test Build Repo CD Release Repo Monitor BuildTest Review/ Appr Deliver Deploy 3rd Party ● Code/Image Build ○ Compilers ○ Code Build - Ant, Maven, Buildbot, Cruisecontrol, etc.
- 17. myRepo Project Repo CI Commit Push Pass/Fail Local Test Build Repo CD Release Repo Monitor BuildTest Review/ Appr Deliver Deploy 3rd Party ● Testing ○ SonarQube ○ Cucumber ○ JUnit ○ Arquillian
- 18. myRepo Project Repo CI Commit Push Pass/Fail Local Test Build Repo CD Release Repo Monitor BuildTest Review/ Appr Deliver Deploy 3rd Party ● Review/Approve ○ Gerrit, Github ● Ticket Update ○ Jira, Redmine
- 19. myRepo Project Repo CI Commit Push Pass/Fail Local Test Build Repo CD Release Repo Monitor BuildTest Review/ Appr Deliver Deploy 3rd Party ● Packaging ○ RPM ● Images ○ Docker, OCI ● Applications/Services ○ Kubernetes, Atomicapp
- 20. myRepo Project Repo CI Commit Push Pass/Fail Local Test Build Repo CD Release Repo Monitor BuildTest Review/ Appr Deliver Deploy 3rd Party ● Anisible,Puppet, Chef ● Atomic/Atomicapp ● Kubernetes ● ManageIQ ● Katella
- 21. myRepo Project Repo CI Commit Push Pass/Fail Local Test Build Repo CD Release Repo Monitor BuildTest Review/ Appr Deliver Deploy 3rd Party ● Tomcat ● Wildfly ● MongoDB ● MySQL ● Vert.x ● Node.js ● Docker ● ActiveMQ ● FeedHenry ● Openstack ● Openshift
- 22. Continuous Integration / ContinuousDeployment Image & Package & Metadata Repository src repo Dev./Build QA Production in OHC Automation Across Environments Events Assets
- 23.
- 24. Continuous Integration / ContinuousDeployment Image & Package & Metadata Repository src repo Dev./Build QA Production in OHC Automation Across Environments Events Assets
- 25. PaaS provides anintegration point
- 26. DEVOPS: THE WHAT &THE WHY CULTURE of collaboration valuing openness and transparency
- 28. Our culture istoo difficult! Really? Consider post war Japan. https://leanhomebuilding.wordpress.com/page/4/
- 29. Impose a cultureof: Empathy Trust Learning Cooperation Responsibility ?
- 31. Issues with just“changing culture” ● Lack of agreed-to model of what “right” culture looks like ● Different organizations require different behaviors ● Culture change is difficult to measure and quantify ● Culture is very hard to impose ● Culture is an output, not an input
- 32. Culture = f(l, o, i, t, …) where: l = leadership o = organization i = incentives t = trust … = many other things Open source offers guidance
- 33. Leadership and visionbut no one organizational structure Multiple models work but characteristics need to fit the project, participants, and vision
- 34. Solve specific problems Opensource projects often begun because of an individual’s interest or issue DevOps projects (often) benefit by tackling low surface area problem cases (But, like open source, DevOps can become the default)
- 35. Transparency Who made changes? Whenand why did they make them? What’s the state of the project? What’s the state of the system? It’s the expectation for both open source and DevOps
- 36. Rich communication flowsmatter Open source projects have been forced to deal with distributed (cross-timezone) teams Tools vary by teams Video getting better F2F time still a big plus
- 37. Don’t fear failure Opensource innovation highly driven by experimentation One of the points of DevOps is to enable better experimentation If it doesn’t work, move on (But fast failures)
- 38. Incentives matter Open sourceprojects (tend to) reward based on merit and contribution Incentives in DevOps organization (advancement, money, recognition) need to reward trust and cooperation Individual has control over their own success
- 39. Open source isdriving DevOps But it’s more than the code!
- 40. Credits Tools: Dorli Photography,cc/flickr https://www.flickr.com/photos/dorlino/4946061042/ Robots: davidgariepy, cc/flickr https://www.flickr.com/photos/davidgariepy/2495011427/ Kids programming: Esti Alvarez cc license Dev: Nelson Pavlosky/flickr under CC http://www.flickr.com/photos/skyfaller/113796919/ Ops: Leonardo Rizzi/flickr under CC http://www.flickr.com/photos/stars6/4381851322/ Rainbows and Unicorns: http://kaigumo.deviantart.com/art/Unicorns-Fart-Rainbows-3-151273843 Join hands: https://www.flickr.com/photos/vogelium/10565496565/ Thanks to J.P.Morgenthal for some of his thoughts about culture change. See also http://www.slideshare.net/JPMorgenthal1/process- andorgtrumpcultureinentdevops Governance models: http://oss-watch.ac.uk/resources/governancemodels Transparent code: iStockPhoto Linux Collaboration Summit: Linux Foundation Wipeout: https://www.flickr.com/photos/andymorffew/15843725192 No: Wikimedia
- 41.