Answer: Good Question! Believe it or Not, our
challenges are not any different than yours.
How are we not different?
Internal PaaS Infrastructure: Puppet Engineering & Delivery
Cloud Infrastructure: Various Web Properties
Not To: Show you how to use Puppet.
The High Points:
Engineer great modules or use known good modules!
Engineer your Puppet code with Roles/Profiles.
Data: What's in your Hiera?
R10k and Dynamic Environments.
Puppet SCM work-flows
Pro Tips: Around Facts and Functions.
Extras: Puppet Tools in the wild that are quite useful.
Understand how a module looks, feels, and is used in your
A few points on Modules:
The life-blood of a great puppet infrastructure are modules.
Strive not to reinvent the wheel - Forge.puppetlabs.com and Github
Be aware, not all modules are created equal.
A good rule of thumb: If your module code is a few yards beyond a simple PFS
pattern then it time to BGTM.
Example: PGPool - https://github.com/jrodriguezjr/puppet-pgpool2
Roles/Profiles In General:
Allows separation of Tech and Business logic in Puppet Code - Craig Dunn, Hunter
Are meant to consume Modules in a logical way.
Allows for Code organization.
Architecture paradigm: For you Devs, its comparative to MVC programming
R10K, Dynamic Environments, & Puppet Work-flows
Adrien Thebo: Author of R10k
If you have more than one dev, look at R10k and Dynamic Environments.
IMHO: It IS the secret to staying agile and developing Puppetcode fast with a Puppet
On Puppet Infrastructure - Hardware (Avoid Puppet drag!)
Anyone running a decent sized puppet infrastructure knows that at times it can be
Run Puppet on a decently sized box!
Preferably one with SSDs, a good amount of procs, and memory.
Building Great Modules.
Roles and Profiles:
R10K and Dynamic Environments:
Great AIO (All-In-One) Series:
Joe Rodriguez (JRod)
Ops Wrangler - Puppet Labs, Inc.