Monty Taylor 967a055c5d Use openstackclient from container
We have multiple places, such as bridge, where we use openstackclient
as a utility. The current practice tends to be installing it into a
venv somewhere. On bridge there are 16 venvs in /root - and in some
of them but not all exist a working openstack client.

Since it's purely an API interaction tool, all it needs is the
clouds.yaml files bind-mounted in. The openstackclient project
now publishes a container image. Install a wrapper script for
calling it into /usr/local on bridge.

Change-Id: I4c64125d5dd3c89275e259a57b0efa0847ac6fc2
2020-04-23 07:46:28 -05:00
2020-02-18 09:29:24 +00:00
2020-02-25 23:17:02 +00:00
2020-02-28 08:10:24 -08:00
2020-02-28 09:30:27 +01:00
2016-07-15 12:04:48 -07:00
2019-04-19 19:26:05 +00:00
2020-02-28 11:06:34 -08: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-01-28 12:46:23 +07: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 156 MiB
Languages
Jinja 37%
Python 36.7%
Shell 13.6%
Dockerfile 3.9%
JavaScript 3%
Other 5.8%