Chapter 2. Configuration Management Standard
This chapter describes the standard of configuration management applied with puppet.
This is a checklist describing the requirements to a puppet setup.
The "default" node applies to all nodes that have do not have a node configuration (yet). The default node should always have a minimal configuration, and a notice to indicate this node is using the default configuration.
See also: Section 4.2, “Initial Manifest”
Assigning variables from facts is helpful; overriding the system's Operating System version allows you to instantly upgrade the OS via puppet.
See also: Section 3.2, “Facts and Variables”, Section 4.3, “Creating Custom Facts”, Section 4.4, “Using Facts and Variables”
Make sure you manage puppet via puppet.
Nothing in a puppet managed environment is as critical as the puppetmaster. You must therefor manage the puppetmaster with puppet as if it is as important as the services that run or facilitate your core-business, to ensure consistency and to not allow sudden (unwanted) changes to it's configuration. Managing the puppetmaster also enables you to pull the manifests, files and modules from a source control management system on a regular schedule. In addition, in environments where the puppetmaster is load-balanced or in a geographically distributed environment, managing the puppetmasters ensures consistency between all of these.
Modules make up a large part of your manifests, allowing you to include modules and submodules for each node and/or group
Use a Source Control Management System for your manifests, files and modules to enable revision control and branching (stable, production, development and testing).
A good configuration management setup allows for different environments such as production , testing and development .
Use a Source Control Management System for your manifests, files and modules to enable revision control and branching (stable, production, development and testing).