continuous delivery & devops in the enterprise

Eberhard Wolff - @ewolff

DevOps & Continuous Delivery

in the Enterprise Eberhard Wolff Freelancer Head Technology Advisory Board adesso AG


Leseprobe: http://bit.ly/CD-Buch


Continuous Delivery DevOps

Adoption


Continuous Delivery: Build Pipeline

Commit Stage

Automated Acceptance

Testing

Automated Capacity Testing

Manual Explorative

Testing

Release


Continuous Delivery •  Pipeline executed several times per day

•  Automated provisioning

•  Fast Feedback •  Tests, tests, tests… •  Feedback from production


Continuous Delivery

in Startups


Lean Startup Approach for launching businesses and products

Relies on •  validated learning •  scientific experimentation •  iterative product releases

To •  shorten product development cycles •  measure progress •  gain valuable customer feedback.


Traditional Approach •  Let’s create a shop 2.0

•  Features •  Express orders •  Improved search •  Improved recommendations


Traditional Approach •  Have it all implemented •  Roll it out •  See impact

•  Spend a lot of money •  Takes a long time •  Can you measure the success?


Lean Startup: Express Orders •  Interview customers

•  No interest

•  Don’t build it


Lean Startup: Search •  Prototype

•  Well received

•  Build it!


Lean Startup: Benefits •  Less money spent

•  Faster results

•  Can further expand e.g. search •  …instead of wasting money on

express orders


Observe

Orient

Decide

Act OODA Loop


Startups •  No clear market yet •  Need feedback •  …and change plan accordingly •  Success depends on speed in OODA

loop


Continuous Delivery and the Market

•  OODA: act quickly, observer better

•  Act: Faster deployment •  = shorter time to market

•  Observe: Better visibility with better monitoring


Continuous Delivery

in Enterprises


IT Faster!

Time to Market!


We used to do a release a quarter.


We used to do a release a quarter.

Now we do one every two quarters


IT Faster!

Time to Market!


Why not? •  Managers think in month •  …or even years

•  Quick feedback and fast deployment hardly usable


So? •  Adopt Lean Startup in Enterprises •  Lean Startup is not just for Startups •  Quicker innovation •  Gain a competitive edge

•  Business strategy •  Outside IT


Software Becomes the Product! •  Example: Automotive •  Cars: Auto pilot (Tesla, Audi) •  Car sharing instead of buying cars •  DriveNow (BMW), Car2Go (Daimler) •  Uber •  MyTaxi (Daimler) •  Enterprise = Start Up?


Continuous Delivery is

faster deployments


Traditional Enterprise Approach

•  Low frequency of releases •  Each release scheduled •  …extensively managed •  …precautions if it fails •  Weekends, nights …

•  Enterprises can only deploy slowly


Enterprises can deploy quickly!


Quick Deployment in Enterprises

Severe production problem •  Hot fix •  Deployed in minutes / hours

How? •  Only limited tests, high risk (?) •  Small batch, small risk


Lessons Learned from Hot Fixes

•  Speed of deployment: no good reason for Continuous Delivery

•  Continuous Delivery = Hot Fix + automated tests

•  Different way to handle risk •  Smaller and faster deployments


Continuous Delivery Minimizes Risk

•  Risk depends on size of change

•  More frequent deployments less risk


Traditional Deployments: Risk

Developer Build

1h

Continuous Integration

Development Environment

1d

Staging

30d

>30d

Production


Continuous Delivery: Risk

Developer Build

1h

Continuous Integration

Acceptance Tests

Capacity Tests

Production


Traditional Enterprise Approach

Difference to Continuous Delivery? •  No automation •  Not reproducible •  Too infrequent to establish best

practices


Full Continuous Delivery Pipeline?

Commit Stage

Automated Acceptance

Testing

Automated Capacity Testing

Manual Explorative

Testing

Release

Dev Ops


Continuous Delivery & Separated Ops

•  Need buy-in from Ops •  Separate organizational unit •  Mistrust •  Used to their ways •  …and tools

•  Solution: DevOps (later)


Dev-only pipeline useful?


Dev-only Pipeline •  Much higher quality •  A lot more tests •  Automated infrastructure •  Pays off for testing systems

•  Sensible alternative


Not just productivity gain

automation vs. manual


Continuous Delivery Pipeline

More frequent

tests

Higher quality

Faster feedback Faster

Time- to-market

Automation

Higher productivity

Reproducible environments


Continuous Delivery in Enterprises: Sum Up

Dev+Ops+Business •  Time to market •  Lean Startup / fast OODA loop •  Best Pay Off Dev + Ops •  Avoid deployment problems •  All the weekends spend on releases


Continuous Delivery in Enterprises: Sum Up

Dev •  Faster feedback •  More tests •  Easier to set up test environments

Can be introduced with little Buy-In •  Just do it!



Adoption


DevOps •  Dev: Development •  Ops: Operations

•  DevOps = close collaboration between Dev and Ops

•  Teams have Ops and Dev people


DevOps in Startups


DevOps in Startups •  You build it – you run it •  Smaller organizational units •  At the beginning: No clear roles •  DevOps teams by feature •  From the start


DevOps in Enterprises


Dev – features Ops – cost


Dev builds it Ops runs it


Why??


Costs


Why Separate Dev and Ops?

•  Adam Smith •  Separation of labor •  Standardization •  Industrialization •  Cost •  Productivity


Lower Costs Differently •  Basic tasks automated by software •  See Continuous Delivery

•  IT = automating tasks


Goals Might Be Different •  Flexible IT to support business •  See Lean Startup etc •  Separate Dev/Ops: not be the best

option for Enterprises?


Let’s introduce DevOps in

Enterprises!


DevOps in Enterprises •  Dev and Ops separated directly

below CIO •  Need to change the organization •  Fundamentally •  Changing the organization is hard

Eberhard Wolff - @ewolff L


DevOps =

Culture


Do you need to change the

organization?


DevOps = Culture •  Let Ops and Dev sit together •  Direct communication between Ops

and Dev engineers emerges •  Associate Ops with Dev teams

•  Share tools… •  …and knowledge


What if you change the

organization?


Traditional Organization

CRM Order Inventory

Dev

Ops Hardware, Operating System etc


Problem with Traditional Organization

•  Customer only cares about applications

•  Not infrastructure •  So: Ops not important? •  Different goals •  Dev: Bring out new features quickly •  Ops: Stable platform and applications


Problem with Traditional Organization

•  At the end Ops and Dev both serve the customer

•  Both own stability and new features

•  But not represented in organization •  …or incentives


DevOps Organization

CRM Order Inventory

Dev

Ops Hardware, Operating System etc Hardware etc


Dev Ops = Customer Oriented

•  Team owns feature •  …and stability •  i.e. value of the application to the

customer •  Clearly responsibility •  Competitive edge for in-house IT



Adoption


DevOps & Continuous

Delivery will be adopted like

Agile


DevOps & CD vs. Agile •  Similar issues •  Culture •  Values •  Time to market

•  E.g. DevOps & CD are the next step after agile


Step 1: Resistance & Doubt •  Agile about 2000 •  eXtreme Programming

•  Management doesn’t want it

•  Doubts whether it can work at all


DevOps & Continuous

Delivery cannot possibly work for

me!


My IT is more complex than

Amazon!


Adoption •  Orthodox to leave the old ways •  Bottom up by IT

•  Problem: Buy-In from Management

•  Current state of DevOps / Continuous Delivery


Step 2: Mainstream •  Developers & technical managers

agree •  No need to discuss the need •  Project start implementing it en

masse •  Agile after 2005


Step 2: Mainstream •  Adoption: Just get a coach •  …but hard to make it truly work •  Values & organization – hard to

change


Step 3: Everyone Is Doing It •  …or at least claims so •  Core values often still not

understood •  …or shared by the organization •  Management Buy-In •  Agile now •  Disillusion


How can DevOps and Continuous

Delivery avoid this?


Customize Continuous Delivery & DevOps for Enterprises


TL;DR


Continuous Delivery in Enterprises

•  Faster time to market •  Useful if business changes

accordingly

•  Otherwise: Lower risk •  Automation & reproducibility •  Smaller batches for releases


DevOps in Enterprises •  DevOps = Culture •  Encourage communication •  …and sharing tools

•  Optional: DevOps = Organization •  Customer Oriented IT •  Optimization for flexibility instead of

cost


Thanks!