cbbceb2330
With the switch to Zuul v3, we need to resolve some configuration catch-22s where project names and related in-repository job definitions can't happen without a complex multi-stage removal and reintroduction process to get it through speculative testing successfully. For now, just punt and use monolithic changes bypassing CI in code review. As an up side, the Ansible automation of this process coupled with Zuul v3's increased resilience to on-the-fly configuration changes means we can skip stopping/starting it now and significantly simplify the process. Since we're here, correct the section heading level for "Force-Merging a Change" in the sysadmin document. Change-Id: I335c23abd0b5706f43bbea2dd8cfffa4280dd5db
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