Monty Taylor c8af267282 Run manage-projects/base/bridge on system-config changes
We should run manage-projects when the manage-projects code on
system-config changes. To do that, we need to run the system-config
playbook so that the system-config content will be updated.

In order to that properly, we need to run base, which means we
need to run bridge. So we really want to do all three so that we're
doing the correct dependent sequence. Subsequent changes can
then just pick off single service playbooks and make them jobs
that depend on base.

Change-Id: I3560feff4309f6be21b72b30a7a6d61a60829e52
2020-03-31 15:37:17 -05:00
2020-03-23 13:16:05 -05:00
2020-03-27 10:02:31 -07:00
2020-03-26 10:36:16 +11:00
2020-03-30 15:57:50 -05:00
2020-03-18 18:23:17 +01:00
2016-07-15 12:04:48 -07:00
2019-04-19 19:26:05 +00:00
2018-11-02 08:19:53 +11:00
2019-04-20 09:31:14 -07:00
2019-05-24 14:56:50 -05:00
2019-04-20 09:31:14 -07:00
2020-03-18 18:23:17 +01:00
2014-09-30 12:40:59 -07:00
2019-04-20 09:31:14 -07:00
2018-06-25 11:19:43 +10: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://opendev.org/opendev/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
Jinja 37%
Python 36.7%
Shell 13.6%
Dockerfile 3.9%
JavaScript 3%
Other 5.8%