Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Continuous Delivery of Puppet-Based Infrastructure - PuppetConf 2014

3,300 views

Published on

Continuous Delivery of Puppet-Based Infrastructure - Sam Kottler, Digital Ocean Puppet

Published in: Technology
  • Be the first to comment

Continuous Delivery of Puppet-Based Infrastructure - PuppetConf 2014

  1. 1. Continuously deploying infrastructure with Puppet Sam Kottler @samkottler https://github.com/skottler shk@linux.com
  2. 2. Why do all (suddenly) seem to Care about this thing?
  3. 3. Deliverability
  4. 4. “Changeability”
  5. 5. Immutability for stateless services ! (more on that later)
  6. 6. The “what” is just a subset of the “How”
  7. 7. Images
  8. 8. Packages
  9. 9. appliances
  10. 10. Environments
  11. 11. Configuration is the heart of the build process
  12. 12. Immutability
  13. 13. Stateless systems often do hold some form of state
  14. 14. There are still (lots of) unsolved problems around orchestration
  15. 15. The result is sometimes Binary
  16. 16. Single Node convergence
  17. 17. Production is generally Composed of many different roles
  18. 18. The pinnacle of infrastructure integration is multi-node orchestration
  19. 19. But what about isolation?
  20. 20. Deliverables
  21. 21. Humans are bad at repetitive tasks
  22. 22. Does it work?
  23. 23. rspec-puppet
  24. 24. Beaker
  25. 25. puppet agent -t
  26. 26. How do we get it live?
  27. 27. Capistrano
  28. 28. r10k
  29. 29. Kafo
  30. 30. Does it Work? …In production
  31. 31. Run puppet via monitoring systems
  32. 32. is it Proper?
  33. 33. puppet-lint
  34. 34. Recap!
  35. 35. Integrate!
  36. 36. Validate!
  37. 37. deliver it!
  38. 38. Thanks! Sam Kottler @samkottler shk@linux.com https://github.com/skottler

×