System configuration for the OpenDev Collaboratory
becdd4b1eb
Add an IRC channel config file with some stub access information for a few channels. A new tool can read this file and verify that openstackinfra has founder access on all the channels listed in the file. Run a job on changes to that file to verify that access is correct. Later, other tools (like statusbot or gerritbot) may read that file directly to determine which channels to join. Or we can at least add checks that all channels referenced by another tool (like eavesdrop) are also listed in this file. Related-Bug: 1190296 Change-Id: I38440e745402af5bbc3f0d0cc04a150c0a4bb47c |
||
---|---|---|
doc/source | ||
launch | ||
manifests | ||
modules | ||
tools | ||
.gitignore | ||
.gitreview | ||
install_jenkins_slave.sh | ||
install_modules.sh | ||
install_puppet.sh | ||
Rakefile | ||
README.md | ||
run_puppet.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
test.sh | ||
tox.ini |
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.