Jeremy Stanley 5221d300fb Correct nodepool max-servers in rax-dfw
* .../templates/nodepool/nodepool.yaml.erb: Since we still have a
handful of long-lived static slaves for sensitive jobs (proposal,
salt-trigger, mirrorXX) along with a couple dev slaves (precise,
centos6) and the remaining four precise-py3k slaves, the effective
capacity for nodepool in rax-dfw is 181. Cut this by a few more so
we have room for template servers during image updates.

Change-Id: I7cdfdba0665fff822fff77c31fa20a6585da411d
2014-02-21 20:30:49 +00:00
2014-01-28 09:32:09 -08:00
2012-11-30 20:56:32 +00:00
2012-09-22 17:32:02 +00:00
2013-09-23 18:29:18 +00:00
2013-09-23 18:29:18 +00:00
2013-12-10 08:36:42 -08:00
2012-09-10 15:58:27 +00:00
2013-11-12 11:30:34 -05:00

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.

Description
System configuration for the OpenDev Collaboratory
Readme 154 MiB
Languages
Jinja 36.9%
Python 36.8%
Shell 13.6%
Dockerfile 3.8%
JavaScript 3%
Other 5.9%