Monty Taylor 851c8c8c13 Run service-bridge in zuul and semaphore everything
Make a base job for the various service playbooks to capture the
fact that we should run these after update-system-config, and if
they run, after both install-ansible and base.

Attach a semphore to the base job, because while many of the
playbooks should be independent, some may not be, and we need to
make sure things don't double-run in periodic and promote.

Transition service-bridge from run_all to zuul, basing it on the
new base job.

While we're in here, reduce manage-projects forks to 10, because
let's face it, that's a more sensible number when there aren't
that many hosts.

Change-Id: I22e9edaea75dcfdab56f667f7c93cdd3ee25406c
2020-04-02 08:25:31 -05:00
2020-03-23 13:16:05 -05:00
2020-03-26 10:36:16 +11:00
2020-04-02 08:19:48 -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%