System configuration for the OpenDev Collaboratory
566e936d98
We only want to start it when we've installed or upgraded. The initial-init and init are designed to either one of them run, one if there is no init script (initial install) the other if there is (upgrade). The things they trigger should only run in response to those actions. Change-Id: I3bcaaed07bcf6239e053789b9b6241cbf652e7d4 |
||
---|---|---|
doc/source | ||
launch | ||
manifests | ||
modules | ||
tools | ||
.gitignore | ||
.gitreview | ||
install_jenkins_slave.sh | ||
install_modules.sh | ||
install_puppet.sh | ||
Rakefile | ||
README.md | ||
run_all.sh | ||
run_puppet.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
test.sh | ||
tox.ini |
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://ci.openstack.org for more information.
Documentation
The documentation presented at http://ci.openstack.org comes from git://git.openstack.org/openstack-infra/config repo's docs/source. To build the documentation use
$ tox -evenv python setup.py build_sphinx