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. A DevOps Toolchain
There and back again
Eric Minick
eric@urbancode.com
@EricMinick
Blogs.urbancode.com
1

2. Software Delivery in a Nutshell
2

3. Apps: More important / More Complex
• More frequent changes
• Lower tolerance for outages
• More complex applications
• More complex deployments
3

4. Software Delivery in a Nutshell
This is broken
4

5. Software Delivery in a Nutshell
Are we
making more How’s the
money? performance?
5

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. That’s DevOps
Embrace faster change and manage
risk by building a collaborative
culture and automating like crazy
7

8. Themes in DevOps Tooling
Shared tools
Lots of automation
Self service XaaS
Version everything
8

9. Example impact on tools: Issue Trackers
9

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. DevOps Toolchains
Span silos
Integrate a collection of a task tool-chains
Dev Test Ops
11 Source http://www.geograph.org.uk/profile/19979

12. Toolchain 1: Build
12

13. Toolchain 2: Deployment
13

14. Toolchain 3: Platform as a Service
14

15. Toolchain 3: Platform as a Service
15

16. Toolchain 4: Test on Deployment
16

17. Toolchain 5: Continuous Delivery / Deploy
17

18. Toolchain 6 – CD with Rollback
18

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 environments
19

20. Where does this get us?
Efficiency
Less manual effort
We avoid rework
Information is easier to find
Less dependence on tribal knowledge
20

21. Where does this get us?
Safety
Error prone manual processes minimized
Deployments of known versions
21

22. Where does this get us?
Visibility
Deployments of known versions
Inventory of what is where
Audit is easy
22

23. Where to start?
23

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. Agree on a Vision
25

26. Begin replacing /
Adding tools
26

27. What’s Normal?
• Ensure at least “ok” build
• Work on the deployment / delivery tool chain
27

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 crazy
28

29. Urbancode Tools
• AnthillPro: Continuous Delivery
• uBuild, CodeStation, uDeploy, uProvision
– More “tool-chainy”
29

30. Other good DevOps tool chain resources
• Gartner:
– DevOps Toolchains Work to Deliver Integratable IT
Process Management”
• Dev2Ops.org
30 http://dev2ops.org/blog/2012/7/23/integrating-devops-tools-into-a-service-delivery-platform-vi.html

31. Urbancode References
http://urbancode.com/html/resources
• White Papers
– Enterprise CD Maturity Model
– Lean Build & Deployment Automation
– Deployment Automation Basics
• Stay in touch:
Blogs.urbancode.com
Twitter.com/UrbanCodeSoftTwitter.com/EricMinick
Slideshare.net/Urbancode
31

32. Q&A
@UrbanCodeSoft
@EricMinick
Slideshare.net/Urbancode
32