c117c1106d
So that we can start running things from the zuul source rather thatn update-system-config and /opt/system-config, we need to install a few things onto the host in install-ansible so that the ansible env is standalone. This introduces a split execution path. The ansible config is now all installed globally onto the machine by install-ansible and does not reference a git checkout. For running ad-hoc commands, an ansible.cfg is introduced inside the root of the system-config dir. So if ansible-playbook is executed with PWD==/opt/system-config it will find that ansible.cfg, it will take precedence, and any content from system-config will take precedence. As a followup we'll make /opt/system-config/ansible.cfg written out by install-ansible from the same template, and we'll update the split to make ansible only work when executed from one of the two configured locations, so that it's clear where we're operating from. Change-Id: I097694244e95751d96e67304aaae53ad19d8b873
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