Building DevOps Toolchain


Published on

How does DevOps impact our tools? This presentation looks at how tools from development to release to monitoring fit together to deliver better for the whole team.

1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Rework: If we use the same deploy tool everywhere, we don’t each create a deployment process
  • =
  • =
  • Building DevOps Toolchain

    1. 1. A DevOps Toolchain There and back again Eric Minick @EricMinick Blogs.urbancode.com1
    2. 2. Software Delivery in a Nutshell2
    3. 3. Apps: More important / More Complex• More frequent changes• Lower tolerance for outages• More complex applications• More complex deployments3
    4. 4. Software Delivery in a Nutshell This is broken4
    5. 5. Software Delivery in a Nutshell Are we making more How’s the money? performance?5
    6. 6. 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.6
    7. 7. That’s DevOpsEmbrace faster change and manage risk by building a collaborative culture and automating like crazy7
    8. 8. Themes in DevOps Tooling Shared tools Lots of automation Self service XaaS Version everything8
    9. 9. Example impact on tools: Issue Trackers9
    10. 10. 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.10
    11. 11. DevOps Toolchains Span silos Integrate a collection of a task tool-chains Dev Test Ops11 Source
    12. 12. Toolchain 1: Build12
    13. 13. Toolchain 2: Deployment13
    14. 14. Toolchain 3: Platform as a Service14
    15. 15. Toolchain 3: Platform as a Service15
    16. 16. Toolchain 4: Test on Deployment16
    17. 17. Toolchain 5: Continuous Delivery / Deploy17
    18. 18. Toolchain 6 – CD with Rollback18
    19. 19. 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 environments19
    20. 20. Where does this get us? Efficiency Less manual effort We avoid rework Information is easier to find Less dependence on tribal knowledge20
    21. 21. Where does this get us? Safety Error prone manual processes minimized Deployments of known versions21
    22. 22. Where does this get us? Visibility Deployments of known versions Inventory of what is where Audit is easy22
    23. 23. Where to start?23
    24. 24. Audit what you have• Where are the bottlenecks?• Where are errors introduced?• Where does the communication stink?24 White Paper: Lean for build and deploy automation
    25. 25. Agree on a Vision25
    26. 26. Begin replacing / Adding tools26
    27. 27. What’s Normal?• Ensure at least “ok” build• Work on the deployment / delivery tool chain27
    28. 28. Key Points• Lots of tools – Build, Deploy, Provision, Config, Test, Monitoring – Multiple vendors: APIs & – Expect and manage overlap• Share tools across silos• Automate like crazy28
    29. 29. Urbancode Tools• AnthillPro: Continuous Delivery• uBuild, CodeStation, uDeploy, uProvision – More “tool-chainy”29
    30. 30. Other good DevOps tool chain resources• Gartner: – DevOps Toolchains Work to Deliver Integratable IT Process Management”• Dev2Ops.org30
    31. 31. Urbancode References• White Papers – Enterprise CD Maturity Model – Lean Build & Deployment Automation – Deployment Automation Basics• Stay in
    32. 32. Q&A @UrbanCodeSoft @EricMinick