Example 42 Puppet Infrastructure¶
Coherent and standardized structure, logic and usage based on best practices
Cross OS support (main targets are Redhat and Ubuntu derivatives)
Use of parametrized classes and fully qualified variables for Puppet 2.8 compliance (on the next generation modules set)
Full and coherent API exposure and classes introspection (on next-gen set)
Separation between core module and user’s customizations, no arbitrary logic enforced.
Optional Puppi support for application deployments and “Puppet knowledge to the CLI”
Optional automatic Monitoring support based on an extensible set of tools
Optional automatic Firewalling support
Decommissioning support: you can remove (almost) whatever you’ve added
Complete documentation compliant with PuppetDoc
Based on common “foo” templates for easy scaffolding on the modules.
Apache 2 Licence
Explore and Download Source¶
Check full “source” on GitHub:
Official Web site is www.example42.com
Tutorial and documentation¶
In order to understand how to use and customize the Example 42 Puppet Infrastructure you should definitively give a look to:
You may also be interested in Puppi, a Puppet module and command line toll that is used to automate application deployments.