c74a4da06e
Our old puppet 4 process was to run the install_puppet.sh script to transition from puppet 3 to puppet 4 but this ran after base.yaml which enforces a puppet version. Unfortunately we were enforcing puppet version 3 in the base.yaml playbook via the puppet-install role which meant base would install pupept 3 and our upgrade playbook would install puppet 4 in a loop. Thankfully we run puppet after the upgrade so we were using the puppet version we wanted. To fix this needless reinstall loop we do two things. We move the upgrade playbook before base.yaml so that we upgrade before we enforce a version. Then we update group vars for the puppet4 group to enforce the puppet 4 version. Change-Id: I97ca81ed5331e664f8e2e65b283793f0919f6033
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