System configuration for the OpenDev Collaboratory
Go to file
Monty Taylor 6bb34219ae Move python-pip include to a class.
You can't have two different classes install the same package (FAIL)
But you can have two different classes include the same class, so
by encapsulating the "install pip" code into a module, we can safely
consume it across multiple modules.

Sometimes I really hate puppet.

Change-Id: I3467c52b6887298c1b4d01a29873c63edf0adfd3
2012-07-23 15:43:27 -05:00
doc Turn off cron and document hiera. 2012-07-21 18:38:51 -07:00
manifests Make a class for each type of server. 2012-07-23 10:33:20 -05:00
modules Move python-pip include to a class. 2012-07-23 15:43:27 -05:00
tools Remove trailing whitespaces in regular file 2012-03-09 16:02:04 +08:00
.gitignore First pass at parameterizing secret infos. 2012-07-20 14:40:42 -07:00
.gitreview Add .gitreview. 2011-10-20 13:37:04 -04:00
README.md Fix README file. It was WAY old. 2012-07-20 16:27:52 -07:00
setup.py Include pep8 target with tox. 2012-06-15 23:27:21 -07:00
tox.ini Include pep8 target with tox. 2012-06-15 23:27:21 -07:00

These are a set of puppet manifests and modules that are currently being used to manage the OpenStack CI infrastructure.

The main entry point is in manifests/site.py.

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.