System configuration for the OpenDev Collaboratory
3ed43ca05f
As we move to using shade through nodepool, several things can consume clouds.yaml via os-client-config. ansible openstack modules can also read the file, as well as python-openstackclient. SO - if we start putting clouds.yaml files places, then we can opt in to using it instead of directories full of shell script env vars. Change-Id: If25ee14f06a4530da4779e062b1ad46238e44f2e |
||
---|---|---|
doc/source | ||
launch | ||
manifests | ||
modules/openstack_project | ||
tools | ||
.gitignore | ||
.gitreview | ||
install_modules.sh | ||
install_puppet.sh | ||
make_swap.sh | ||
modules.env | ||
mount_volume.sh | ||
Rakefile | ||
README.md | ||
roles.yaml | ||
run_all.sh | ||
run_puppet.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
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/system-config repo's docs/source. To build the documentation use
$ tox -evenv python setup.py build_sphinx