the devops imperative

32
The DevOps Imperative Why Ops Must Change and How

Upload: ibm-urbancode-products

Post on 11-May-2015

2.111 views

Category:

Technology


0 download

DESCRIPTION

Why is DevOps all the rage? In this presentation I argued that operations is under a great deal of pressure from changing infrastructure and business climates. Operations is going to need to change, and the core changes it needs to make are in line with the foundations of DevOps.This presentation has a number of "image" slides. If you want to hear the words that go with thing, watch the replay of the presentation. Available here: http://www.urbancode.com/html/resources/webinars/The_DevOps_Imperative.html

TRANSCRIPT

Page 1: The DevOps Imperative

The DevOps Imperative

Why Ops Must Change and How

Page 2: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Changing climate for IT Infrastructure & Ops

Ops

Page 3: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Business Pressures

Applications are more critical

Faster time to market

Less tolerance for outage

Global audience

Page 4: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Methodology Pressure

Agile and Lean (startup)

Source: Bethesda Photography: http://www.flickr.com/photos/alexanderkafka/5554945690/

Page 5: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Infrastructure

Larger Scale, Greater Complexity and Clouds

Gartner survey found most viewed their environments as “very complex” (50%), or “out of control” (17%)

* Source: “Catalysts Signal the Growth of DevOps” Cameron Haight - Gartner Feb 2012 . I performed the calculations.

Page 6: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

But is it a perfect storm?

Page 7: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Ex: Agile + Business Pressures

Agile: Parallel Development

Business: Short cycle

times

Demand: New Test

Env. in Minutes

Page 8: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Plus an increasingly viable alternative

Demand: New Test

Env. In Minutes

Alternative:Cloud PaaS

Deliver or..

“It is not necessary to change. Survival is not mandatory” - Deming

Page 9: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

I could do this all day Need: Automated Deployments:

­ Shorter Test Cycles + More Dev Change ­ Larger scale + Shorter Outage Windows­ More Releases + Can’t Add Staff

Need: Automated Configuration Application­ Larger Scale + More Moving Parts + More Change

Need: Better Dev / Ops Collaboration­ More new apps + Less Time to Plan­ Performance Critical + Perf Tests Stink

Need: Awesome redundancy / failover­ More critical apps + More internal / external risk

Page 10: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

EmbraceChange

Page 11: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Embrace­Change

ManageRisk

Page 12: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Embrace­Change

ManageRisk

Collaborate­with­App-Dev

Page 13: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Embrace­Change

AutomateEverything

ManageRisk

Collaborate­with­App-Dev

Page 14: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

That’s DevOps

“We embrace faster change and manage risk by building a collaborative culture and automating like crazy.”

Page 15: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Velocity: not just speed

Page 16: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Feedback is key

• Deliver Quickly• Test Often• Monitor Production

Page 17: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

DevOps is Directional not a Road-map

Page 18: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Four areas to improve

Source: Patrick Debois: http://jedi.be/blog/2012/05/12/codifying-devops-area-practices/

Page 19: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

“Tool chain” not “tool”

Dev to Prod to Dev

Page 20: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Collaboration will require Silo-busting

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

Dev Test Ops

DevOps

Page 21: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Collaboration will require Silo-busting

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

Dev Test Ops

Beware, Conway’s Law

DevOps

Page 22: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Four strategies for facing Conway’s Law

1. Hire engineers that have skills in development, test and system administration

Page 23: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Four strategies for facing Conway’s Law

1. Hire engineers that have skills in development, test and system administration

2. Put together cross functional teams

Page 24: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Four strategies for facing Conway’s Law

1. Hire engineers that have skills in development, test and system administration

2. Put together cross functional teams3. Create a “DevOps Infrastructure Team”

Page 25: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Four strategies for facing Conway’s Law

1. Hire engineers that have skills in development, test and system administration

2. Put together cross functional teams3. Create a “DevOps Infrastructure Team”4. Fight through it!

­ There’s nothing keeping you from asking, “How do I make your life easier?”

Page 26: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Practices: What to Google after this event

Devs wear pagers Test environments on

demand Version control of

environment definitions Zero downtime

deployments Automated database

deployments

Release manifests & snapshots

Developers attend release post-mortems

Ops included in product planning.

Routine failover testing Production immune system Canary deployments

Page 27: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

The industry is already moving this way

Infrastructure support teams have been doing this for years

Gartner survey*: “…even though the concept itself is still somewhat ambiguous, a significant number of organizations (47%) are in some phase of experimenting with DevOps.”

* Source: “Catalysts Signal the Growth of DevOps” Cameron Haight - Gartner Feb 2012 .

Page 28: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Key Points

Ops will change­ Apps critical + complex infrastructure + agile/lean

DevOps­ Embraces change and manages risk­ By collaborating and automating

Page 29: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Book club

Page 30: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

More References

http://urbancode.com/html/resources

Creating a DevOps Team that Isn’t Evil Lean Build & Deployment Automation Deployment Automation Basics

Blogs.urbancode.comTwitter.com: @UrbancodeFacebook.com/UrbanCodeSoftSlideshare.net/Urbancode

Page 31: The DevOps Imperative

UrbanCode, an IBM Company. Proprietary and Confidential ©2013

Yes, we sell DevOps oriented products

uBuild ­ Build automation and CI for the hard problems

uDeploy­ Deployment and release management

uRelease­ Plan and execute major release efforts spanning many

applications

Page 32: The DevOps Imperative

Q&A@UrbanCodeSoft

@EricMinickSlideshare.net/Urbancode