9 dev ops erik peet - demystifying devops

15
Demys&fying DevOps through experimen&ng Erik Peet Rabobank Nederland [email protected]

Upload: nmitsymposium

Post on 10-Aug-2015

132 views

Category:

Technology


0 download

TRANSCRIPT

Demys&fying  DevOps  

through  experimen&ng  

Erik  Peet  Rabobank  Nederland  

[email protected]  

DevOps  

Movement  Philosophy  Community  

Collaboration  Multidisciplinary  Dev  +  Ops  +  …  

Resilience  

Culture  Automation  

Lean  Metrics  Sharing  

Rabobank  Nederland  

•  Based  on  my  experience  as  a  projectmanager  in  commercial  lending  area  (Financieren  Bedrijven)  and  current  posi&on  as  an  IT  Opera&ons  manager  

•  Business  is  important  part  of  the  process  but  focus  is  on  DevOps  •  Two  story  lines:    

−  Interven&ons  −  Structure  of  slides  on  phasing  DevOps:  people,  process,  tools  and  characteris&cs  

Introduc&on  

Process  

People  

Characteris&cs  

Tools  

Rabobank  Nederland  

•  Conflic&ng  interest  and  KPI’s:  dev  change,  ops  stability  •  Ops  comes  in  at  the  end  of  the  project:  no  ops  requirements,  PAT  in  a  squeeze  •  Working  from  different  loca&ons  •  Working  from  different  departments  

DevOps  phase  1:  two  separate  worlds  

Changing the bank

Running the bank

Nieuwegein   Zeist  

Rabobank  Nederland  

5

Interven9on  #1  

Experiment! And sometimes go dark till you got something to show

Rabobank  Nederland  

•  Ops  is  part  of  the  scrum  team  •  Working  (parWme)  at  the  same  loca&on  •  User  stories  are  reviewed  against  Ops  guidelines  •  PAT  is  not  done  as  part  of  the  sprint  

DevOps  phase  2:  par&cipa&on  

Changing the bank

Running the bank

Nieuwegein   Zeist  

Rabobank  Nederland  

7

Interven9on  #2  

Rabobank  Nederland  

•  Con&nuous  delivery:  build,  test,  provisioning  and  deployment  are  automated  •  PAT  is  part  of  the  sprint/DoD  •  One  dedicated  team  

DevOps  phase  3:  automa&on  

Changing the bank

Running the bank

Nieuwegein   Zeist  

Rabobank  Nederland  

9

Interven9on  #3  

Rabobank  Nederland  

Measure and im

prove continuously

Zeist  

•  Monitor  and  capture  the  right  metrics,  con&nuously  improve  •  Show  it  on  dashboards,  show  added  value  •  3LS  for  incidents  is  handled  by  the  scrum  team  •  Dev  is  involved  in  problem  analysis,  problems  are  on  the  backlog  •  Share  knowledge,  setup  communi&es  

DevOps  phase  4:  closing  the  loop    

Changing the bank

Running the bank

Nieuwegein  

Rabobank  Nederland  

11

Interven9on  #4  

Rabobank  Nederland  

•  Ops  picks  up  tasks  to  meet  the  sprint  commitment  •  Dev  handles  incidents  and  problems  •  One  set  of  KPI’s  •  Shared  responsibility  for  Dev  and  Ops  •  One  department  

DevOps  phase  5:  symbiosis  

Changing the running bank

Product(ion) backlog Nieuwegein  

Rabobank  Nederland  

13

Interven9on  #5  

Rabobank  Nederland  

You can’t cheat you have to go through all the phases

DevOps  phase  3:  automa&on  

Summary  DevOps  phases  &  interven&ons  

Interven9ons:  1.  Experiment  2.  Automate  3.  Measure  and  

improve  con&nuously  4.  Re-­‐organize  5.  Go  through  all  the  

phases  

DevOps  phase  1:  two  separate  worlds  

DevOps  phase  2:  par&cipa&on  

DevOps  phase  5:  symbiosis  

DevOps  phase  4:  closing  the  loop    

Rabobank  Nederland  

15

Just do it Just take the first step

Rabobank  Nederland