c2fc3cd018
Since our infrastructure signing key includes a unique comment field in its name which changes with the key each cycle when it's rotated, we need to explicitly let Git know how to identify the key (it doesn't automatically rely on the default secret key in the keychain and instead expects that any optional comment be part of the name). Use an E-mail address to identify the signing key to Git since this will remain the same through rotation, and since the jenkins::jenkinsuser module completely replaces the keyring files we can simply insure our process only ever sets one key for that address in the provided keyring contents (which is how we document doing it already). Change-Id: I78fe7fa331ae9b51ff0fbf91c0c2f8961b09eb88 Depends-On: Id577c4479abd2f443f73c630a12e94d3ebe63660
Puppet Modules
These are a set of puppet manifests and modules that are currently being used to manage the OpenStack Project infrastructure.
The main entry point is in manifests/site.pp.
In general, most of the modules here are designed to be able to be run either in agent or apply mode.
These puppet modules require puppet 2.7 or greater. Additionally, the site.pp manifest assumes the existence of hiera.
See http://docs.openstack.org/infra/system-config for more information.
Documentation
The documentation presented at http://docs.openstack.org/infra/system-config comes from git://git.openstack.org/openstack-infra/system-config repo's docs/source. To build the documentation use
$ tox -evenv python setup.py build_sphinx