Clark Boylan 0269710c86 Don't manage puppet.conf during puppet-install
The ansible-role-puppet role manages puppet.conf for us. These two roles
are currently fighting each other over the presence of the server line
in puppet.conf. Avoid this by removing the removal of this line and the
templatedir line from the new puppet-install role since
ansible-role-puppet was there first. Basically just trust
ansible-role-puppet to write a working puppet.conf for us.

Change-Id: Ifb1dff31a61071bd867d3a7cc3cbcc496177e3ce
2019-04-08 10:09:35 -07:00
2019-04-05 17:29:24 -07:00
2019-02-14 16:39:12 -08:00
2019-03-26 15:31:50 -07:00
2016-07-15 12:04:48 -07:00
2018-11-02 08:19:53 +11:00
2019-03-08 14:18:28 -08:00
2014-09-30 12:40:59 -07:00
2018-06-25 11:19:43 +10:00
2018-06-25 11:19:43 +10:00
2019-03-06 18:42:39 +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://docs.openstack.org/infra/system-config for more information.

Documentation

The documentation presented at http://docs.openstack.org/infra/system-config comes from https://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 153 MiB
Languages
Python 37.2%
Jinja 36.6%
Shell 13.6%
Dockerfile 3.8%
JavaScript 3%
Other 5.8%