Designing Puppet Catalogs
summary
Practical prescription: enforce one role per server and structure code as roles-profiles-modules so modules do all resource work, profiles only include modules, and roles include profiles. Put runtime configuration in Hiera, keep hierarchies small for performance, and set a role fact at boot (an init script) so node definitions are three lines. Prefer use contains (or anchor) for ordering, make modules own each resource, and add tests; the pattern reduces surprising conflicts.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:55Why Puppet
- 2:09Things Got Weird
- 2:54Cloud Environment
- 5:03Frameworks
- 6:12Modules
- 8:42Profiles
- 10:43Hierarchy
- 11:17Roles
- 22:38Apache
- 24:45Puppet Hierarchy
- 33:11Conclusion
related talks
42mPuppet Control-Repo to the Next Level
15mPuppet and containers: A multi-tenancy deployment
25mConfiguration Management vs. Workflows vs. Orchestration
44mPatterns for infrastructure-as-code
55mManaging PostgreSQL with Puppet
37mPUPPET SYSTEMS INFRASTRUCTURE CONSTRUCTION KIT
36mPuppet Under Load
44mQuick Prototyping with LXC and Puppet