puppet camp phoenix 2015:my soul has a price: selling management and developers on puppet (beginner)

My Soul has a PriceSelling management and developers on Puppet

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

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

2 stages

• Pre - Gather your info and present it

• During - Planning, development and deployment

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”

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

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.

Why Dogs?

They can be trained to do anything.

Almost.

Mcollective

• Automation

• Config Consistency

• Build Consistency

• Security and Compliance

• Rapid Deployment

• 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

Time Savings

It’s pretty.

For managers.

Reports

Ease of Use

Control

Ease of Use

Managed Items

Ease of Use

Accountability

Collectives

What version of a packageTime Savings

Restarting a service

Control

Check file differences

Ease of Use

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

They’re sold!!! Now what?

Phase II: Development and Implementation

• Communicate

• Put your plan in an easily accessible place

• Address Concerns

• Be Available

Questions?