The document discusses continuously deploying infrastructure with Puppet. It covers topics like deliverability, immutability, configuration as the heart of the build process, orchestration challenges, isolation, validation tools like rspec-puppet and Beaker, and deployment tools like Capistrano and r10k. The goal is to integrate infrastructure, validate configurations, and reliably deliver changes to production environments.

1. Continuously
deploying
infrastructure with
Puppet
Sam Kottler
@samkottler
https://github.com/skottler
shk@linux.com

3. Why do all (suddenly)
seem to Care about
this thing?

4. Deliverability

5. “Changeability”

6. Immutability for
stateless services
!
(more on that later)

7. The “what” is just a
subset of the “How”

8. Images

9. Packages

10. appliances

11. Environments

12. Configuration is
the heart of the
build process

13. Immutability

14. Stateless systems
often do hold some
form of state

15. There are still
(lots of) unsolved
problems around
orchestration

16. The result is
sometimes Binary

17. Single Node
convergence

18. Production is
generally Composed
of many different
roles

19. The pinnacle of
infrastructure
integration is multi-node
orchestration

22. But what about
isolation?

23. Deliverables

24. Humans are bad at
repetitive tasks

25. Does it work?

26. rspec-puppet

27. Beaker

28. puppet agent -t

29. How do we get it live?

30. Capistrano

31. r10k

32. Kafo

33. Does it Work?
…In production

34. Run puppet via
monitoring systems

35. is it Proper?

36. puppet-lint

37. Recap!

38. Integrate!

39. Validate!

40. deliver it!

41. Thanks!
Sam Kottler
@samkottler
shk@linux.com
https://github.com/skottler