From Fedora Project Wiki

(Mention search in /etc/resolv.conf)
(Oops, it was already in another SOP. My bad.)
Line 68: Line 68:
=== On the node ===
=== On the node ===
Make sure that is in the search path in /etc/resolv.conf, then do a manual run of puppet:
Do a manual run of puppet:
puppetd -t --server=puppet
puppetd -t --server=puppet

Revision as of 04:11, 12 June 2008

Puppet SOP


This page is intended for people who are already familiar with puppet. It is specific to our Fedora Infrastructure though the techniques are general enough to apply to other environments.


All of our configs and manifests are stored in CVS. We also have a private CVS that stores keys, certificates and other files (like sudoers) that shouldn't be messed with or altered but by a select few people.

The following commands will check out all cvs configs (from

cvs -d /cvs/puppet co configs
cvs -d /cvs/puppet co manifests

Altering config files

The config files need to be edited, saved and installed. The following example assumes everything is checked out already and is to alter a proxy file on the webserver.

cd configs
vi web/
cvs commit -m "altered the wiki config"
make install

Puppet Infrastructure SOP/code

Adding new files

Adding new files consists of two things, adding the file and adding the manifest. Adding the config file is similar to the alteration section above. Just add the file to the appropriate directory, cvs add filename. Then commit and run 'make install'

Once the config file is in place move to your manifests directory and add the file to whichever manifest seems appropriate. If none do, add a new manifest. All of our manifests exist in the services directory. From there the servergroups manifests group the services into logical machines. The nodes file then includes those servergroups for submission to the servers.

Adding new node

Adding new hosts of an already known type is easy. The following example is for a builder. First check out the manifests module. Then add a new node file (see other node files for an example:)

For example

node xenbuilder3{
include build

The "include build" line refers to a 'build' group in the servergroups directory.

Node Access

If this is a new node coming from a previously un-used IP address. We need to give puppet, infrastructure and the accounts system access to the node:

cvs -d /cvs/puppet co manifests
cd manifests
vi fileserver.conf
cvs commit -m "What you added"
make install
cd ..
cvs -d /cvs/puppet co configs
cd configs
vi web/
vi web/exclude.conf.erb

On the node

Do a manual run of puppet:

puppetd -t --server=puppet

This initial run will send a certificate request over to the puppet master. once you have signed the new request (below) go back to the node and re-run the command.

Signing new ca request

If using one of our official kickstart scripts a server will automatically request a cert from puppet1. To view a list just run (as root)

puppetca --list

followed by a sign of whatever hostname needs to be signed:

puppetca --sign


Sometimes a new node needs to have puppet restarted in order to connect correctly after its certificate has been approved. Simply log in and run 'service puppet restart'

Remove Server

To remove a server first clean the cert:

puppetca -c

Then remove its node file.

Regenerate cert request

To regenerate the cert request (for example when re-kicking a box) first remove the old cert

puppetca -c

then restart puppet on the remote node. Then sign the certificate as mentioned above with --sign