David Patterson, Apollo Global

1. My Soul has a Price
Selling management and developers on Puppet

2. About me
• David Patterson - david.patterson@apollo.edu - david@damnetwork.net
• Using linux since approx ’95 - Are you on my lawn?
• As an admin since late 90’s
• Went from small Co. -> Enterprise
• Yggdrasil, Slackware, Redhat, OEL, Mandrake, Debian, Gentoo, and yes, Ubuntu.
• Currently Apollo Global
• Puppet for approx 2 years
• Still consider myself a newbie with Puppet

3. Why?
You *have* to have approval and buy-in.

4. 2 stages
• Pre - Gather your info and present it
• During - Planning, development and deployment

5. Management
Benefits Concerns
Control Time Savings
Stability Cost of Tool
Reports Cost of Time to Implement
Graphs Accountability

6. Developers
Benefits Concerns
Consistency Control
Speed Managed Items
Stability Accountability
Ease of Use “Another PITA tool. Ugh”

7. Configuration Management
I hope this works, it’s my first second third.

8. My Philosophy
• Provide stable, secure, consistent servers
• Dev/Apps and Ops are symbiotic
• Provide documentation
• Provide Dev/Apps everything they need to
do *their* job

9. Our current state:
Cats.
• They do what they want.
• They answer to no-one.
• They go where they want.
• I don’t like cats.

11. Why Dogs?
They can be trained to do anything.

12. Almost.

13. Mcollective

14. • Automation
• Config Consistency
• Build Consistency
• Security and Compliance
• Rapid Deployment

15. • Automation
• Config Consistency
• Build Consistency
• Control
• Control
• Control
• Security Compliance
• Speed
• Control
• Rapid Deployments
• Control
• Control
• Control
• Control
• Control
Stability
Control
Consistency
Speed

16. Separate the data
from the code.
• Hierarchal data
• host -> app -> role -> Env -> DC
• One place to change data
• Less repetition
• Quickly add new hierarchy
• No changes to puppet code

18. TimeSavings

19. It’s pretty.
For managers.

20. Reports

23. Ease of Use
Control

27. Ease of Use
Managed Items

28. Ease of Use

29. Accountability

30. Collectives

31. What version of a package
TimeSavings

32. Restarting a service
Control

33. Check file differences
Ease of Use

34. Feb March April May June July Aug
RP Dev
RP QA
RP Prod
UK Dev
UK QA
UK Prod
I HAVE A TIMELINE!!!
Sorta..

35. What’s next?
• Build Automation
• Access Control
• Easy Reporting
• Patching
• Lots of beer time for the linux dudes

36. They’re sold!!! Now what?

37. Phase II:
Development and Implementation
• Communicate
• Put your plan in an easily accessible place
• Address Concerns
• Be Available

38. Questions?