Spencer Krum 4cc08edcd3 Set modulepath to the first element of puppet's modulepath.
This duplicates the behavior of puppet module install for the git
clone operations.

Puppet module install will use the first element of the modulepath.
This makes the git clone operations go into the same directory as
the modules installed via the puppet module tool.

This helps us downstream because we are moving the directory that
holds these modules out of /etc/ and into /opt/.

Change-Id: I0c7833a6d9a79fa613efc9daebee916f3192306a
2015-01-22 02:41:20 -08:00
2014-06-27 12:48:59 -07:00
2015-01-09 09:54:58 +11:00
2015-01-20 14:12:13 +00:00
2014-09-30 12:40:59 -07:00
2014-08-27 15:30:56 -04:00
2013-09-23 18:29:18 +00:00
2014-10-20 18:35:44 +00:00

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
System configuration for the OpenDev Collaboratory
Readme 154 MiB
Languages
Python 37.2%
Jinja 36.6%
Shell 13.6%
Dockerfile 3.8%
JavaScript 3%
Other 5.8%