Downloaded 730 times
Uploaded byIBM UrbanCode Products
How to Build a DevOps Toolchain
The document discusses DevOps toolchains which integrate development and operations tools to improve software delivery. It provides examples of toolchains for activities like continuous integration, deployment, testing, and monitoring. The key benefits are cited as increased efficiency, consistency, safety, and visibility across the development and operations processes. The document recommends auditing current practices, agreeing on a vision, and gradually adopting tools to achieve DevOps.
More Related Content
![Customer Relationship Management - Case Study [Mercedes Benz]](https://cdn.slidesharecdn.com/ss_thumbnails/erpcrm-150303130533-conversion-gate01-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to How to Build a DevOps Toolchain
![Accelerating Software Delivery [Decoding DevOps Conference - InfoSeption]](https://cdn.slidesharecdn.com/ss_thumbnails/decodingdevopsapr2015nareshchoudharyshareablepdf-150727174655-lva1-app6891-thumbnail.jpg?width=640&height=640&fit=bounds)
How to Build a DevOps Toolchain
- 1. © 2013 IBMCorporation A DevOps Toolchain There and back again Eric Minick eminick@us.ibm.com @EricMinick
- 2. © 2013 IBMCorporation Software Delivery in a Nutshell Biz Idea! Dev ♫ Codes / Tests "Make This!" Ops "Ship It" Release / Monitor
- 3. © 2013 IBMCorporation Apps: More Important / More Complex More frequent changes Lower tolerance for outages More complex applications More complex deployments Biz Idea! Dev ♫ Codes / Tests "Make This!" Ops "Ship It" Release / Monitor
- 4. © 2013 IBMCorporation Software Delivery in a Nutshell Biz Idea! Dev ♫ Codes / Tests "Make This!" Ops "Ship It" Release / Monitor This is broken
- 5. © 2013 IBMCorporation Software Delivery in a Nutshell Biz Idea! Dev ♫ Codes / Tests "Make This!" Ops "Ship It" Release / Monitor Are we making more money? How’s the performance?
- 6. © 2013 IBMCorporation Apps: More Important / More Complex More frequent changes Lower tolerance for outages More complex applications More complex deployments Need: Fix the Dev to Ops hand-off for speed / reliability, and deliver better visibility into production performance.
- 7. That’s DevOps Enterprisecapability for continuous software delivery that enables organizations to seize market opportunities and reduce time to customer feedback Continuous Embrace Change Manage Risk Collaborate Automate Customer Feedback & Optimization Collaborative Development Continuous Business Planning Steer Operate Develop/ Test DevOps Deploy Continuous Release and Deployment Continuous Monitoring Continuous Testing © 2013 7 IBM Corporation
- 8. © 2013 IBMCorporation Themes in DevOps Tooling Shared tools Lots of automation Self service *aaS Version everything Biz Idea! Dev ♫ Codes / Tests Agile Reqs. Ops Faster / Safer Release / Monitor Feedback Loops Everywhere
- 9. © 2013 IBMCorporation Example impact on tools: Issue Trackers
- 10. © 2013 IBMCorporation Example impact on tools: Issue Trackers Shared Tools: Within a project, have a common backlog for development and infrastructure tasks. Automation: Make sure you have APIs available to automatically create / migrate tickets based on tests, monitoring, deployments.
- 11. Integrate a collectionof a task tool-chains © 2013 IBM Corporation DevOps Toolchains Span silos DDeevv TTeesstt OOppss Source http://www.geograph.org.uk/profile/19979
- 12. © 2013 IBMCorporation Toolchain 1: Build Source Repos Continuous Integration & Build Mgmt. Static Analysis Build Registered with Package Build Package Repo Build Script / Compiler Dependency Management Unit Tests Repo Triggers Basic Build Loop Version Meta-data
- 13. © 2013 IBMCorporation Toolchain 2: Deployment Package Repo Deployment Engine Manifest Creation Test 1 Test 2 Test n Prod Environment Config Environment Inventory Builds
- 14. © 2013 IBMCorporation Toolchain 3: Platform as a Service Source Repos Env. Def Package Repo Deployment Chain Test 1 Test 2 Test n Prod Version Meta-data Pattern Engine and Controller Images IaaS Provisioning Server Configuration Environment Config Environment Inventory
- 15. © 2013 IBMCorporation Toolchain 4: Test on Deployment Package Repo Deployment Chain Test 1 Test ... Test n Prod Test Tools Builds Version Meta-data
- 16. © 2013 IBMCorporation Toolchain 5: Continuous Delivery / Deploy Source Repos Continuous Integration & Build Mgmt. Build Package Repo Build Registered with Package Repo Triggers Version Meta-data Deployment System Builds Test 1 Test ... Test n Prod Functional Tests Performance Tests Monitoring
- 17. © 2013 IBMCorporation Toolchain 6 – CD with Rollback Source Repos Continuous Integration & Build Mgmt. Build Package Repo Build Registered with Package Repo Triggers Version Meta-data Deployment System Builds Test 1 Test ... Test n Prod Functional Tests Performance Tests Monitoring Rollback Event Correlation
- 18. © 2013 IBMCorporation Where does this get us? Efficiency Less manual effort We avoid rework Information is easier to find Less dependence on tribal knowledge
- 19. © 2013 IBMCorporation Where does this get us? Consistency Tasks required to deliver tracked in one place CI and “official builds” unified Same deployment tool for all environments Same infrastructure tool in all environments
- 20. © 2013 IBMCorporation Where does this get us? Safety Error prone manual processes minimized Deployments of known versions
- 21. © 2013 IBMCorporation Where does this get us? Visibility Deployments of known versions Inventory of what is where Audit is easy
- 22. © 2013 IBMCorporation Where to start?
- 23. IBM DevOps adoptionmodel New practices, tools and services to plan and execute a staged adoption of DevOps to improve business outcomes Inefficient Leaner Leaner and Smarter Steer Product-based Develop/Test Deploy Operate Efficiency Productive Waste Agile Automated Collaborative Optimizing More Predictable More Transparent More Continuous Process-based Process-heavy Manual Silo-ed Feedback cycles © 2013 23 IBM Corporation
- 24. © 2013 IBMCorporation Audit what you have Where are the bottlenecks? Where are errors introduced? Where is communication weak? Use our assessment tool https://ibm.biz/devops-practices-assessment
- 25. © 2013 IBMCorporation Agree on a Vision
- 26. © 2013 IBMCorporation Roadmap path forward
- 27. © 2013 IBMCorporation Begin adopting tools
- 28. What’s Normal? Leftto Right, then Right to Left. © 2013 IBM Corporation 1. Ensure at least “ok” build 2. Work on the deployment / delivery tool chain 3. Attach feedback mechanisms opportunistically Source Repos Continuous Integration & Build Mgmt. Build Package Repo Build Registered with Package Repo Triggers Version Meta-data Deployment System Builds Test 1 Test ... Test n Prod Functional Tests Performance Tests Monitoring
- 29. © 2013 IBMCorporation Key Points Lots of tools –Build, Deploy, Provision, Config, Test, Monitoring –Multiple vendors: APIs & Direct Integrations –Expect and manage overlap Share tools across silos Automate Aggressively
- 30. © 2013 IBMCorporation An IBM heavy tool chain
- 31. © 2013 IBMCorporation Other good DevOps tool chain resources Gartner: –“DevOps Toolchains Work to Deliver Integratable IT Process Management” Dev2Ops.org http://dev2ops.org/blog/2012/7/23/integrating-devops-tools-into-a-service-delivery-platform-vi.html
- 32. © 2013 IBMCorporation UrbanCode References http://developer.ibm.com/urbancode White Papers –Enterprise CD Maturity Model –Deployment Automation Basics Stay in touch https://developer.ibm.com/urbancode/blog/ Twitter.com/UrbanCode Twitter.com/EricMinick Slideshare.net/UrbanCode
- 33. © 2013 IBMCorporation Q&A @UrbanCode @EricMinick Slideshare.net/urbancode Developer.ibm.com/urbancode/
Editor's Notes
- #8 Main point: DevOps is an enterprise capability for continuous software delivery that enables clients to seize market opportunities and reduce time to customer feedback ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Here is the IBM definition of DevOps. It enables clients to: Accelerate software delivery - by enabling collaboration between customers and enterprises and eliminating organizational silos Balance speed, cost, quality and risk- By automating manual processes and eliminating waste Improve client experience - By speeding the customer feedback loop Notes: ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- “Companies that master effective software development and delivery in rapidly changing environments such as cloud, mobile and social will have a significant competitive advantage,” - Kristof Kloeckner, general manager, IBM Rational Software.
- #19 Rework: If we use the same deploy tool everywhere, we don’t each create a deployment process
- #21 =
- #22 =