The Birth of DevOps

The Birth of DevOps

From 2½ Days to 2½ Seconds - the Birth of DevOps

This is an experience report from the mid-2000s, where a fifty-person programme team was being held up by test environments that took an average of 2½ days to prepare. By developing strategies like Blue/Green Deployments, the Single Deployable Artifact, Container Templates, the Build Production Line and many of the other principles that led to Continuous Delivery, we brought this down to only a few minutes, with a near-instantaneous cutover for the users. The legendary team included the likes of Julian "Build Doctor" Simpson, Chris Read, Sam Newman and both the authors of the Continuous Delivery book, only one of whom swore a lot. Dan North is not the father of DevOps but he may be its midwife. He definitely assisted at the birth.

08145ecb1ce091d9dd3c328ea2a707fb?s=128

Daniel Terhorst-North

June 19, 2014
Tweet

Transcript

  1. 1.

    From 2½ days to 2½ seconds - the birth of

    DevOps Dan North @tastapod
  2. 4.

    Once upon a time… back in the mists of 2005

    before Continuous Delivery™
  3. 5.

    Once upon a time… back in the mists of 2005

    before Continuous Delivery™ a team was stuck.
  4. 6.

    Once upon a time… back in the mists of 2005

    before Continuous Delivery™ a team was stuck. This is their story.
  5. 9.

    Life was tough back then 2½ days to deploy a

    build Testers were frustrated!
  6. 10.

    Life was tough back then 2½ days to deploy a

    build Testers were frustrated! Developers were frustrated!
  7. 11.

    Life was tough back then 2½ days to deploy a

    build Testers were frustrated! Developers were frustrated! We were bottlenecked at testing :(
  8. 12.

    Life was tough back then 2½ days to deploy a

    build Testers were frustrated! Developers were frustrated! We were bottlenecked at testing :( actually bottlenecked at deployment!
  9. 21.
  10. 22.

    Where do we start? "Elevate the constraint" Engage Operations as

    customer Understand the manual steps Identify where time is being sunk
  11. 23.

    Where do we start? "Elevate the constraint" Engage Operations as

    customer Understand the manual steps Identify where time is being sunk Focus on the outcome, not the steps
  12. 27.

    Idea: Treat the container as code WebLogic is just XML

    so create templates and version-control them!
  13. 36.
  14. 37.

    Idea: Make all the servers look the same Same OS

    Same packages Same versions Same(ish) settings
  15. 43.

    Conan the Deployer - Create a new container instance -

    Generate container config - Deploy container config
  16. 44.

    Conan the Deployer - Create a new container instance -

    Generate container config - Deploy container config - Bring up the master node
  17. 45.

    Conan the Deployer - Create a new container instance -

    Generate container config - Deploy container config - Bring up the master node - Deploy the app into the node
  18. 46.

    Conan the Deployer - Create a new container instance -

    Generate container config - Deploy container config - Bring up the master node - Deploy the app into the node - Bring up the app
  19. 47.

    Conan the Deployer - Create a new container instance -

    Generate container config - Deploy container config - Bring up the master node - Deploy the app into the node - Bring up the app - Smoke test the environment
  20. 51.

    This was the big breakthrough Any build into any environment

    2½ days down to 25 minutes! Deterministically.
  21. 59.

    What did we learn? Focus on the outcome Focus on

    the current bottleneck You don't "have an investment" in hardware
  22. 60.

    What did we learn? Focus on the outcome Focus on

    the current bottleneck You don't "have an investment" in hardware DevOps requires collaboration
  23. 61.
  24. 63.

    Epilogue Sam Newman develops DbDeploy Jez Humble and Chris Read

    (and me :) describe the Build Production Line
  25. 64.

    Epilogue Sam Newman develops DbDeploy Jez Humble and Chris Read

    (and me :) describe the Build Production Line Chris Read co-creates DevOps Days
  26. 65.

    Epilogue Sam Newman develops DbDeploy Jez Humble and Chris Read

    (and me :) describe the Build Production Line Chris Read co-creates DevOps Days Julian Simpson becomes the Build Doctor
  27. 66.

    Epilogue Sam Newman develops DbDeploy Jez Humble and Chris Read

    (and me :) describe the Build Production Line Chris Read co-creates DevOps Days Julian Simpson becomes the Build Doctor Jez Humble and Dave Farley write “Continuous Delivery” and win Jolt Award
  28. 71.

    Whither DevOps? Commoditise All the Things! Cloud All the Things!

    Hug a SysAdmin today And remember: A “build team” is still an anti-pattern!