
We have several tox environments that don't really share the same dependencies. Currently we put everything into test-requirements.txt, meaning the linter environment gets testinfra and testinfra environment gets things like ansible-lint it's not using. Apart from being a bit faster not installing things, this is helpful for restoring the ansible -devel test. In that case, we have ansible as a project dependency; when installing from git, ansible now installs itself as "ansible-base" ("ansible" is the released pypi package that incorporates collections). So if we install ansible-lint in the testinfra environment, this pulls in ansible ... and then it breaks when tox wants to install our Zuul clone of upstream ansible (you can't have ansible and ansible-base together). Change-Id: I5f3fc93e6ddd611f319fa269e122ed576c9cb378
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
Languages
Python
37.2%
Jinja
36.6%
Shell
13.6%
Dockerfile
3.8%
JavaScript
3%
Other
5.8%