DevOps Isn’t Just for WebOps: The Guerrilla’s Guide to Cultural Change

5,443 views

Published on

DevOps has been a hot topic for several years, but it’s nearly always talked about with respect to web operations and startups. Since DevOps starts culturally, you can take a bottom-up approach and create a DevOps mindset inside your organization, even if you’re not deploying code twenty times a day.

Michael Stahnke
Director of Software Engineering, Puppet Labs
Michael Stahnke is a Software Engineering Director at Puppet Labs, where he was previously the Community Manager and where he built out the Release Engineering team as Release Manager. He came to Puppet Labs from Caterpillar, Inc. where he was an Infrastructure Architect, system administration team lead, and open source evangelist. Michael also helped get the Extra Packages for Enterprise Linux (EPEL) repository off the ground in 2006, and is the author of Pro OpenSSH (Apress, 2005).

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,443
On SlideShare
0
From Embeds
0
Number of Embeds
2,860
Actions
Shares
0
Downloads
59
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

DevOps Isn’t Just for WebOps: The Guerrilla’s Guide to Cultural Change

  1. 1. DevOps Isn’t Just for WebOps: The Guerrilla’s Guide to Cultural Change Michael Stahnke Engineering Director | Puppet Labs @stahnma Saturday, August 24, 13
  2. 2. puppetconf.com #puppetconf Saturday, August 24, 13
  3. 3. puppetconf.com #puppetconf Saturday, August 24, 13
  4. 4. puppetconf.com #puppetconf “It is impossible to exceed expectations.” Saturday, August 24, 13
  5. 5. puppetconf.com #puppetconf “Nobody ever got a high-five for a server staying up” Saturday, August 24, 13
  6. 6. puppetconf.com #puppetconf Saturday, August 24, 13
  7. 7. puppetconf.com #puppetconf Saturday, August 24, 13
  8. 8. puppetconf.com #puppetconf Saturday, August 24, 13
  9. 9. puppetconf.com #puppetconf Saturday, August 24, 13
  10. 10. puppetconf.com #puppetconf Saturday, August 24, 13
  11. 11. puppetconf.com #puppetconf Saturday, August 24, 13
  12. 12. puppetconf.com #puppetconf Saturday, August 24, 13
  13. 13. puppetconf.com #puppetconf Saturday, August 24, 13
  14. 14. puppetconf.com #puppetconf Saturday, August 24, 13
  15. 15. puppetconf.com #puppetconf Saturday, August 24, 13
  16. 16. puppetconf.com #puppetconf Saturday, August 24, 13
  17. 17. puppetconf.com #puppetconf Saturday, August 24, 13
  18. 18. puppetconf.com #puppetconf Saturday, August 24, 13
  19. 19. puppetconf.com #puppetconf Saturday, August 24, 13
  20. 20. puppetconf.com #puppetconf Saturday, August 24, 13
  21. 21. puppetconf.com #puppetconf Saturday, August 24, 13
  22. 22. puppetconf.com #puppetconf Saturday, August 24, 13
  23. 23. puppetconf.com #puppetconf Saturday, August 24, 13
  24. 24. puppetconf.com #puppetconf “Reduce the standard deviation value. Then raise the mean.” Saturday, August 24, 13
  25. 25. Method 1: Reduce Variability Saturday, August 24, 13
  26. 26. puppetconf.com #puppetconf “Do you want your systems to have planned or unplanned downtime? Because you’re going to get one or the other.” Saturday, August 24, 13
  27. 27. puppetconf.com #puppetconf Saturday, August 24, 13
  28. 28. puppetconf.com #puppetconf Saturday, August 24, 13
  29. 29. puppetconf.com #puppetconf Collaboration? Saturday, August 24, 13
  30. 30. puppetconf.com #puppetconf Saturday, August 24, 13
  31. 31. puppetconf.com #puppetconf Saturday, August 24, 13
  32. 32. puppetconf.com #puppetconf Saturday, August 24, 13
  33. 33. Method 2: Stop. Collaborate. Listen. ( Break down silos ) Saturday, August 24, 13
  34. 34. puppetconf.com #puppetconf Saturday, August 24, 13
  35. 35. puppetconf.com #puppetconf Saturday, August 24, 13
  36. 36. puppetconf.com #puppetconf Saturday, August 24, 13
  37. 37. puppetconf.com #puppetconf Saturday, August 24, 13
  38. 38. Method 3: Shout your failures. (Honesty builds credibility) Saturday, August 24, 13
  39. 39. puppetconf.com #puppetconf Saturday, August 24, 13
  40. 40. puppetconf.com #puppetconf Saturday, August 24, 13
  41. 41. puppetconf.com #puppetconf Saturday, August 24, 13
  42. 42. puppetconf.com #puppetconf Saturday, August 24, 13
  43. 43. puppetconf.com #puppetconf Saturday, August 24, 13
  44. 44. Method 4: Experimentation Matters. (Failures are still valid data) Saturday, August 24, 13
  45. 45. puppetconf.com #puppetconf Saturday, August 24, 13
  46. 46. puppetconf.com #puppetconf Saturday, August 24, 13
  47. 47. puppetconf.com #puppetconf Saturday, August 24, 13
  48. 48. puppetconf.com #puppetconf Saturday, August 24, 13
  49. 49. puppetconf.com #puppetconf Saturday, August 24, 13
  50. 50. puppetconf.com #puppetconf “The cost of retiring any technology is much higher than introducing it” Saturday, August 24, 13
  51. 51. puppetconf.com #puppetconf Saturday, August 24, 13
  52. 52. puppetconf.com #puppetconf Saturday, August 24, 13
  53. 53. puppetconf.com #puppetconf Saturday, August 24, 13
  54. 54. puppetconf.com #puppetconf Saturday, August 24, 13
  55. 55. Method 5: Solve Causes Not Symptoms (Continuous Improvement) Saturday, August 24, 13
  56. 56. Recap • Reduce Variability. • Stop. Collaborate. Listen. • Shout your failures. • Experimentation Matters. • Solve Causes Not Symptoms. Saturday, August 24, 13
  57. 57. Sidebar: Rockstars don’t fix everything. Ask me how I know. Saturday, August 24, 13
  58. 58. puppetconf.com #puppetconf Saturday, August 24, 13
  59. 59. puppetconf.com #puppetconf Saturday, August 24, 13
  60. 60. puppetconf.com #puppetconf Saturday, August 24, 13
  61. 61. Follow us on Twitter @puppetlabs youtube.com/puppetlabsinc slideshare.net/puppetlabs Collaborate. Automate. Ship. Saturday, August 24, 13

×