Ian Wienand b3c01b30b3 install-ansible: move install_modules.sh to puppet-setup-ansible
Modules are collected on bridge and then synchronized to remote hosts
where puppet is run.  This is done to ensure an atomic run of puppet
across affected hosts.

These modules are described in modules.env and cloned by
install_modules.sh.  Currently this is done in install-ansible, but
after some recent refactoring
(I3b1cea5a25974f56ea9202e252af7b8420f4adc9) the best home for it
appears to now be in puppet-setup-ansible; just before the script is
run.

Change-Id: I4b1d709d7037e2851d73be4bc7a202f52858ad4f
2020-09-03 09:28:16 +10:00
2020-07-03 07:17:22 +10:00
2020-08-11 13:15:06 -07:00
2020-06-17 14:51:58 -07:00
2020-08-06 09:42:39 +10:00
2020-08-11 13:15:06 -07:00
2020-06-09 10:15:05 +10: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
2020-06-05 12:09:30 -05:00
2019-04-20 09:31:14 -07:00
2014-09-30 12:40:59 -07:00
2020-04-06 18:19:28 +00:00
2018-06-25 11:19:43 +10:00
2020-07-15 07:03:22 +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
Python 36.8%
Jinja 36.8%
Shell 13.6%
Dockerfile 3.9%
JavaScript 3%
Other 5.9%