System configuration for the OpenDev Collaboratory
fc98399aa4
In implementing the library to consume the service-types data, it became clear that the behavior could be much more consistent across implementations if we set cache-control headers. This allows a combined ETag and time-based approach, so that the data will only be fetched if it has a stale etag, but it will only be checked for staleness once a week. Since the data in question is expected to change only rarely, and then only in additive ways, this should allow pervassive use of the data without significant cost to the API consumer. Change-Id: I6de3c79e22fdea9bf70fd725447ca7141af80b50 |
||
---|---|---|
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