One Does Not Simply Walk into Devops

DevOps is much more than tooling and technical details, it’s first and foremost a cultural and operational shift. This deck was given at www.devopscon.com, and covers some of the principles and best practices preached for by devops thought leaders such as John Allspaw, Jesse Robbins, Adrian Cockroft, Jez Humble and others.

Transcript

2. Some   Background  
3. A  Few   Defini5on   A6empts  
4. “stresses   communica(on  &   collabora(on  ...     aims  to  help  an   organiza2on  rapidly   produce  so3ware   products  and   services”  
5. “The  DevOps   movement  was   born  of  the  need  to   improve  IT  service   delivery  agility...  “  
6. Jesse  Robbins,   OpsCode   “Some  of  that  is   tools  ...  A  big  part  of   that  is  culture”  
7. Adrian  Cockro@,   NeBlix     “Help  me  define  it…”                
9. So…  What  Is   It  about?   It’s  about  shipping   be6er  so@ware,   faster  &  more   consistently     •  Where  tradi0onal  dev   and  ops  roles  fail  to   deliver    
10. Learn  by  example,  not  invent     (yet)  another  defini5on…  
11. Jesse’s   Taxonomy     (I  know,  this  can  also   start  a  flame  war…)   Dev  &  Ops  as  Teams   (Culture  &  Processes)   Infrastructure  as  Code   Applica0on  as  Services    
13. Accountability   •  sdf   hBp://www.slideshare.net/jezhumble/scaling-­‐devops  
14. Trust  &   Responsibility     Allspaw’s  Take     Devs  own  their   code,  so  they   expect  24x7   contact  with  it  
15. Trust  &   Responsibility     Allspaw’s  Take     When  things   break,  dev  and   ops  both   par0cipate    
16. Trust  &   Responsibility     Allspaw’s  Take     Post  mortems   have  dev  and  ops   remedia0ons    
17. “Everyone  who  has   changes  going  out   is  accounted  for  and   is  ac2vely  tes2ng   and  suppor2ng   their  changes”   Chuck  Rossi,   Facebook  
19. hBp://www.slideshare.net/jesserobbins/hacking-­‐culture-­‐at-­‐velocityconf     Defini5on  of  Done  
20.   Jez  Humble   “Done  means   released”  
21.     Measure   Everything   “If  it  moves,  graph   it.  If  it  maHers,  alert   on  it”   Allspaw  
22.   Not  Just   Infrastructure   •  Measure  infra,  app   and  business  KPIs   •  Don’t  just  measure,   correlate  
23. hBp://www.slideshare.net/jallspaw/dev-­‐and-­‐ops-­‐collabora0on-­‐and-­‐awareness-­‐at-­‐etsy-­‐and-­‐flickr    
24. Paint  the  Walls   hBp://www.slideshare.net/realgenekim/2012-­‐velocity-­‐london-­‐devops-­‐paBerns-­‐dis0lled    
25. Chuck  Rossi,   Facebook   “Ship  early,     ship  o@en”   •  Small  increments   •  Undeployed  code  is   lost  value    
26. hBp://www.slideshare.net/jallspaw/ops-­‐metametrics-­‐the-­‐currency-­‐you-­‐pay-­‐for-­‐change    
27. hBp://www.slideshare.net/jallspaw/ops-­‐metametrics-­‐the-­‐currency-­‐you-­‐pay-­‐for-­‐change    
28. hBp://www.slideshare.net/jallspaw/ops-­‐metametrics-­‐the-­‐currency-­‐you-­‐pay-­‐for-­‐change    
29. hBp://www.slideshare.net/jallspaw/ops-­‐metametrics-­‐the-­‐currency-­‐you-­‐pay-­‐for-­‐change    
30. 11.6  seconds   Mean  0me  between  deployments     1079   Max  number  of  deployments  /  hour       10,000     Mean  number  of  hosts  simultaneously   receiving  a  deployment             Source:  John  Jenkins  
32. Well  Defined   Rollout   Mechanism   •  Canary  tests   •  Red/Black   Deployment   •  Dark  launches    
33. hBp://www.slideshare.net/bi^ield/agile-­‐sysadmin-­‐and-­‐the-­‐art-­‐of-­‐infrastructure-­‐automa0on-­‐2493286    
38. A  Self-­‐ Service  Data   Center  Really   Helps   (Even  more  so  if   it  has  an  API..)    
39. The  Common   to  All  the   Above   •  Infrastructure  as   product,  app  devs   as  customers     – NeBlix  calls  it  NoOps,   but  it  pisses  of  Allspaw  
41. •  Small  services   with  APIs   – Easier  to  ship,  easier  to   debug,  easier  to   manage  at  large  scale   – Caveat:  forward  and   backward  compa0bility   – @adrianco’s  “an0-­‐ fragility”    
42. Resiliency  in   the  So@ware   Stack     •  We  assume   commodity  HW,   Cloud   •  So  we  have  to   build  reliability   into  our  code    
43. Feature  Flips   hBp://www.flickr.com/photos/maxabxarata/535048895/    
45. Jeremy  Edberg,     NeBlix   “Everything  is   Built  for  3”        
46. Circuit  Breakers  (NeBlix)  
47. Fire  Drills  &   Monkeys…  
48. What’s  Next?   – Not  everyone  is   Amazon  &  Ne^lix     – The  next  challenge  is   to  make  this   accessible  to  all