Why Puppet? Why now? Can you get by without using any config management? You probably think don't have time, or that your project is too small. What can using Puppet really add? How can you justify investing time up front? Maybe you can just do it later? Getting started with config management can often seem like a big project, especially if you only manage a few systems or have a small team. This talk will examine why you should use Puppet from the beginning. It will examine what you can do with Puppet that couldn't do otherwise, how much time it will save and why it's especially important if you think your project has even the smallest chance of scaling in the future. Presented by David Mytton at Puppet Camp London 2015-04-13

1. Why Puppet? Why now?
Puppet Camp, London 2015
David Mytton, CEO, Server Density

2. David Mytton

4. serverdensity.com/knocknock

5. Agenda
• Objection handling
• Cloud
• Use cases
• Basics - why Puppet?

6. Why Puppet?

7. Why config management?
• Similar: why source control?

8. Why config management?
• Infrastructure as code
• Similar: why source control?

9. Why config management?
• Infrastructure as code
• Versioned infrastructure
• Similar: why source control?

10. Why config management?
• Infrastructure as code
• Versioned infrastructure
• Consistency
• Similar: why source control?

11. Why config management?
• Infrastructure as code
• Versioned infrastructure
• Consistency
• Similar: why source control?
• Readability

12. Why config management?
• Infrastructure as code
• Versioned infrastructure
• Consistency
• Similar: why source control?
• Readability
• Audits

13. Use cases
• Package deployment

14. Use cases
• Versions (pinning)
• Package deployment

15. Use cases
• Versions (pinning)
• Config files / templates
• Package deployment

16. Use cases
• Versions (pinning)
• Config files / templates
• Tweaks, fixes, patches
• Package deployment

17. Why Puppet?
• PuppetDB: Your infrastructure in a database

18. Why Puppet?
• Hiera: Your config in a database
• PuppetDB: Your infrastructure in a database

19. Why Puppet?
• Hiera: Your config in a database
• Facter: Your infrastructure analytics
• PuppetDB: Your infrastructure in a database

20. Why Puppet?
• Hiera: Your config in a database
• Facter: Your infrastructure analytics
• Forge: Open source your infrastructure
• PuppetDB: Your infrastructure in a database

21. Why Puppet?
• Hiera: Your config in a database
• Facter: Your infrastructure analytics
• Forge: Open source your infrastructure
• PuppetDB: Your infrastructure in a database
• PE Console: Your infrastructure GUI

22. Objection handling
• I only have a few servers

23. Objection handling
• Do you plan to grow?
• I only have a few servers

24. Objection handling
• Do you plan to grow?
• I only have a few servers
• Do you want a consistent environment?

25. Objection handling
• Do you plan to grow?
• I only have a few servers
• Do you want a consistent environment?
• Destroy/redeploy

26. Objection handling
• It’s too complex

27. Objection handling
• Initial investment
• It’s too complex

28. Objection handling
• Initial investment
• It’s too complex
• Saves time with changes later

29. Objection handling
• Initial investment
• It’s too complex
• Saves time with changes later
• Similar: programming libraries -> Forge

30. Objection handling
• I’ll just SSH manually

31. Objection handling
• Mistakes
• I’ll just SSH manually

32. Objection handling
• Mistakes
• I’ll just SSH manually
• Security

33. Objection handling
• Mistakes
• I’ll just SSH manually
• Security
• Audit

34. Objection handling
• I’ll write a few shell scripts

35. Objection handling
• Scale
• I’ll write a few shell scripts

36. Objection handling
• Scale
• I’ll write a few shell scripts
• Idempotency

37. Objection handling
• Scale
• I’ll write a few shell scripts
• Idempotency
• Version control?

38. Cloud
• Re-deploy around failures

39. Cloud
• Re-deploy around failures
• Consistency across many instances

40. Cloud
• Re-deploy around failures
• Consistency across many instances
• Managing large clusters

41. Cloud
• Re-deploy around failures
• Consistency across many instances
• Managing large clusters
• Querying facts

42. Use cases
• Deploys

43. Use cases

44. Use cases

45. Use cases

46. Use cases
• Deploys
• Docs

47. Use cases
• Deploys
• Docs
• Failover

48. Why Puppet?
• Hiera: Your config in a database
• Facter: Your infrastructure analytics
• PuppetDB: Your infrastructure in a database

49. ありがとうございます
david@serverdensity.com
@davidmytton