Toolserver:Admin:Puppet

Puppet is a configuration engine for hosts. It uses a definition of how each host should be configured, and changes the host until it matches the desired configuration. We use Puppet for distributing configuration files, installing (and upgrading) software, and enabling services. Puppet only runs on the Solaris systems.

Puppet consists of two parts, the puppetmaster which runs on a single server and serves the configuration information, and puppetd which runs on each host and applies the configuration. The puppetmaster runs on the HA cluster under the 'puppet' resource group. Its configuration is in /global/misc/puppet.

Puppet normally runs from cron every 30 minutes. If you want to force a run before then (e.g. to test configuration changes), run /opt/ts/sbin/puppetd -t.

Editing configuration files
Most configuration files are in /global/misc/puppet/etc/modules/ /files/. Basic configuration files are in the base module. Other modules contains task-specific configuration files. Note that there might be several copies of one configuration file, usually one in base and one in an overriding module.

When you edit a configuration file, remember it will be propagated to every host. Don't put host-specific things in it.

The Puppet configuration is stored in Git. When you change anything, run 'git commit' to commit your changes. Also, remember to open a MNT issue for every change.

Installing software
Puppet handles installing software. Before configuring the software to be installed, you should build a package, probably using pkgbuild. Then edit the appropriate software cluster manifest; these are stored under /global/misc/puppet/etc/modules/software/manifests. For software that should be installed on every host, add it to misc_std. For login servers only, add it to misc_user. Do not include the "TS" prefix; the Puppet configuration will add it automatically.