System configuration for the OpenDev Collaboratory
aec4d5fb39
Through testing we have discovered that every vos release affects remote AFS caches. It appears that doing a vos release (even one that is a nop) causes remote AFS clients to update file metadata info on file read. This affects are pypi mirror in particular because we vos release on it every 5 minutes. Make this less costly in the pypi mirror by checking which packages are updated by bandersnatch against our upper constraints list and only vos release if the package is in upper constraints. We will also vos release if 4 hours has passed since the last vos release to catch any packages not listed in constraints. Change-Id: Ib79393300111ba300cbea92200b6d8e729672354 |
||
---|---|---|
doc/source | ||
hiera | ||
launch | ||
manifests | ||
modules/openstack_project | ||
playbooks | ||
tools | ||
.gitignore | ||
.gitreview | ||
bindep.txt | ||
Gemfile | ||
install_modules.sh | ||
install_puppet.sh | ||
make_swap.sh | ||
modules.env | ||
mount_volume.sh | ||
Rakefile | ||
README.md | ||
roles.yaml | ||
run_all.sh | ||
run_bifrost.sh | ||
run_cloud_launcher.sh | ||
run_infracloud.sh | ||
run_puppet.sh | ||
setup.cfg | ||
setup.py | ||
start_all_zuul.yaml | ||
stop_all_zuul.yaml | ||
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://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