
This causes apply-test.sh to get the list of puppet modules to do integration test with from modules.env. Modules.env has been refactored to have three lists of modules: Package modules(MODULES), SOURCE_MODULES, and INTEGRATION_MODULES. When PUPPET_INTEGRATION_TEST is not set, INTEGRATION_MODULES is folded into SOURCE_MODULES. In apply-test.sh, INTEGRATION_MODULES is sourced from modules.env and some string/array manipulation is performed to pass each entry to zuul-cloner. Change-Id: I47302c5c7e8c41b985f16a05c4e9b8078ea867a3
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
Description
Languages
Python
37.2%
Jinja
36.6%
Shell
13.6%
Dockerfile
3.8%
JavaScript
3%
Other
5.8%