4f0342be70
Sharing an updates file between the Debian and Ubuntu reprepro runs causes some warnings, and is generally just unclean. They use different release naming and repositories, so should just have separate updates files to track them (they're already separate on the server, they were just being copied from the same source file in the module). While here, remove the label and suite parameters from the Debian reprepro distribution templates, as they're unnecessary and potentially confusing (job nodes should never be relying on the suite names as they change at the next release). Also allow signatures from subkeys of the listed keys to be sufficient to verify the debian-security mirror's release files, like we do for the debian mirror. Change-Id: Id0ff476864f936bbd7c4637f3dc9e2c219c6e465
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