DevOps Days Melbourne meet-up

Post on 29-Nov-2014

1.316 views 3 download

description

This is a talk I gave at the DevOps days meet-up in Melbourne in June 2012.In the talk I go over implementing Continuous Delivery in an enterprise organisation. Its based on our experiences doing CD in a large traditional Telco in Australia.It covers:- an introduction to the principle- the state of the art of Cont. Delivery in Single application versus multistream development- the optimum conditions to start implementing and measuring CD- focusing on the BAU/Support line as an entry point

Transcript of DevOps Days Melbourne meet-up

Tales  from  the  wild  

Con2nuous  Delivery    

@nigelfds  

github.com/nigelfds  

We  shall  do  Con2nuous  Delivery  

Great  Message!  

Really  difficult  execu2on  

Silver  Bullet  Syndrome  

Its  about  Risk  

“I  do  believe  that  complexity  is  the  enemy.  Un7l  we  be9er  understand  complexity,  our  chances  of  building  be9er  IT  systems  is  limited.  The  first  thing  we  must  understand  about  complexity  is  that  not  all  complexity  is  equal.  And  the  complexity  on  which  most  people  focus  is  probably  the  least  complex  complexity  of  all.”  

hHp://simplearchitectures.blogspot.com/2009/03/cancer-­‐of-­‐complexity.html  

Roger  Sessions  

Deployment    v  

 Configura2on  Management    v  

 Test  Automa2on    

Single  Stream  

Mul2-­‐team/Mul2-­‐stream  

Op2mum  condi2ons  

Cycle  2me  

Batch  size  

Stability  

High  value  

Sounds  crazy?  

It  already  exists  in  your  company  

They  just  call  it  

VCS  

BAU  

Tac2cal  

Programme  

Test   Prod  Staging  Ar2fact  

Test  Ar2fact   Test  Merge  with    Trunk  

Test  Ar2fact   Test   Merge  with    Trunk  

Trunk  

The  pit  stop  crew  is  king  

Keep  the  turn  around  2me  low  

VCS  

Tac2cal  

Programme  

Test   Prod  Staging  Ar2fact  

Test  Ar2fact   Test  Merge  with    Trunk  

Test  Ar2fact   Test   Merge  with    Trunk  

Trunk  

3  MONTHS  

1  DAY  

2  WEEKS  

Keep  the  path  to  produc2on  clear  

VCS  

Tac2cal  

Programme  

Test   Prod  Staging  Ar2fact  

Test  Ar2fact   Test  Merge  with    Trunk  

Test  Ar2fact   Test   Merge  with    Trunk  

Trunk   8  hours  then  back-­‐out  

Encourage  the  right  behaviors  

Pressure  on  longer  cycles  to  merge  more  o`en  

Pressure  to  keep  batch  size  small  

Pressure  to  release  more  o`en      

Summary  

This  stuff  is  hard  to  get  right  

A  great  place  to  start  is  the  produc2on  support  line  

Thank  you