Building DevOps Toolchain

1

A DevOps Toolchain

There and back again

Eric Minickeric@urbancode.com@EricMinick

Blogs.urbancode.com

2

Software Delivery in a Nutshell

3

Apps: More important / More Complex

• More frequent changes• Lower tolerance for outages• More complex applications• More complex deployments

4

Software Delivery in a Nutshell

This is broken

5

Software Delivery in a Nutshell

Are we making more

money?

How’s the performance?

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.

7

That’s DevOps

Embrace faster change and manage risk by building a collaborative culture and automating like crazy

8

Themes in DevOps Tooling

Shared tools

Lots of automation

Self service XaaS

Version everything

9

Example impact on tools: Issue Trackers

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.

11

DevOps Toolchains

Source http://www.geograph.org.uk/profile/19979

Dev Test Ops

Span silosIntegrate a collection of a task tool-chains

12

Toolchain 1: Build

13

Toolchain 2: Deployment

14

Toolchain 3: Platform as a Service

15

Toolchain 3: Platform as a Service

16

Toolchain 4: Test on Deployment

17

Toolchain 5: Continuous Delivery / Deploy

18

Toolchain 6 – CD with Rollback

19

Where does this get us?

Consistency

Tasks required to deliver tracked in one placeCI and “official builds” unifiedSame deployment tool for all environmentsSame infrastructure tool in all environments

20

Where does this get us?

Efficiency

Less manual effortWe avoid reworkInformation is easier to findLess dependence on tribal knowledge

21

Where does this get us?

Safety

Error prone manual processes minimizedDeployments of known versions

22

Where does this get us?

Visibility

Deployments of known versionsInventory of what is whereAudit is easy

23

Where to start?

24

Audit what you have

• Where are the bottlenecks?

• Where are errors introduced?

• Where does the communication stink?

White Paper: Lean for build and deploy automation

25

Agree on a Vision

26

Begin replacing / Adding tools

27

What’s Normal?

• Ensure at least “ok” build

• Work on the deployment / delivery tool chain

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

29

Urbancode Tools

• AnthillPro: Continuous Delivery

• uBuild, CodeStation, uDeploy, uProvision – More “tool-chainy”

30

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

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.comTwitter.com/UrbanCodeSoft Twitter.com/EricMinickSlideshare.net/Urbancode

32

Q&A

@UrbanCodeSoft@EricMinick

Slideshare.net/Urbancode