Post on 15-Jul-2015
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
ManagementBenefits Concerns
Control Time Savings
Stability Cost of Tool
Reports Cost of Time to Implement
Graphs Accountability
DevelopersBenefits Concerns
Consistency Control
Speed Managed Items
Stability Accountability
Ease of Use “Another PITA tool. Ugh”
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
Our current state: Cats.
• They do what they want. • They answer to no-one. • They go where they want. • I don’t like cats.
• Automation
• Config Consistency
• Build Consistency
• Control
• Control
• Control
• Security Compliance
• Speed
• Control
• Rapid Deployments
• Control
• Control
• Control
• Control
• Control
Stability
Control
Consistency
Speed
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
Feb March April May June July Aug
RP Dev
RP QA
RP Prod
UK Dev
UK QA
UK Prod
I HAVE A TIMELINE!!! Sorta..
What’s next?• Build Automation • Access Control • Easy Reporting • Patching • Lots of beer time for the linux dudes
Phase II: Development and Implementation
• Communicate
• Put your plan in an easily accessible place
• Address Concerns
• Be Available