Colleen Murphy 1bd9635d97 Use openstack_project::server class where possible
As we move configuration for zuul worker nodes out of puppet and into
DIB elements, we should keep track of what is being managed by puppet
for long-lived servers and what no longer needs to be managed for single
use workers. The openstack_project::server class wraps the
openstack_server::template class which stores configuration that is
common to both types of machines. This patch updates the backup_server
and lists class to use the openstack_project::server class, updating
class parameters where they differ between o_p:server and o_p::template.
This way we can chop down the template class and move bits into the
server class until eventually we can entirely remove the
openstack_project::single_use_slave and openstack_project::template
classes.

Change-Id: Ief997d608a3a1632ec34da34ec46a237ead761f5
2017-04-07 21:56:17 +02:00
2017-04-06 16:35:56 -04:00
2016-07-15 12:04:48 -07:00
2016-06-02 10:47:36 +03:00
2014-09-30 12:40:59 -07:00
2017-03-02 20:09:39 +01:00
2017-03-02 20:09:39 +01:00
2017-01-12 15:32:46 -05: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://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

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%