System configuration for the OpenDev Collaboratory
b55ed05a27
We'd like to be able to control sequencing of how and when puppet runs across our machines. Currently, it's just a set of agents that run kinda whenever they run. At times they hang and we don't know about it. Also, cross-server sequencing is impossible to achieve. Change the operation away from agents running on the machine as daemons, and instead ssh from the master to each machine. Change-Id: I76e41e63c6d0825e8735c484ba4580d545515e43 |
||
---|---|---|
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