66a95e5224
It also seems that Ansible became more strict about the permissions of the current working directory[1] so we need to either move our ansible.cfg to a better location, or get rid of it. In the zuul test environment, the location is world-writable. Given that this is an ansible.cfg used for tests only, that its content is (mostly) duplicated in the wrapper's RC file and that implementation of avoiding the wrapper was done when we had vars plugins (which we no longer have), I think it's safe to remove it and use the wrapper instead. Using the wrapper ensures that everything is set in one place, so it's easier to find. In the AIO bootstrap we then just make sure we override things that we do not want to interfere with the AIO bootstrap - then unset them later so that the defaults get applied from then on. To also reduce the duplication of the bootstrap-aio.sh script in the gate-check-commit script, we source bootstrap-aio from gate-check-commit. [1]: |
||
|---|---|---|
| deploy-guide/source | ||
| doc | ||
| etc | ||
| inventory | ||
| osa_toolkit | ||
| playbooks | ||
| releasenotes | ||
| scripts | ||
| tests | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| LICENSE.txt | ||
| README.rst | ||
| Vagrantfile | ||
| ansible-role-requirements.yml | ||
| ansible-role-requirements.yml.example | ||
| bindep.txt | ||
| global-requirement-pins.txt | ||
| requirements.txt | ||
| run_tests.sh | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Team and repository tags
OpenStack-Ansible
OpenStack-Ansible is an official OpenStack project which aims to deploy production environments from source in a way that makes it scalable while also being simple to operate, upgrade, and grow.
For an overview of the mission, repositories and related Wiki home page, please see the formal Home Page for the project.
For those looking to test OpenStack-Ansible using an All-In-One (AIO) build, please see the Quick Start guide.
For more detailed Installation and Operator documentation, please see the Deployment Guide.
If OpenStack-Ansible is missing something you'd like to see included, then we encourage you to see the Developer Documentation for more details on how you can get involved.
Developers wishing to work on the OpenStack-Ansible project should always base their work on the latest code, available from the master GIT repository at Source.
If you have some questions, or would like some assistance with
achieving your goals, then please feel free to reach out to us on the OpenStack Mailing Lists
(particularly openstack-operators or openstack-dev) or on IRC in
#openstack-ansible on the freenode network.
OpenStack-Ansible Roles
OpenStack-Ansible offers separate role repositories for each individual role that OpenStack-Ansible supports. For individual role configuration options, see the Role Documentation.
An individual role's source code can be found at: https://git.openstack.org/cgit/openstack/openstack-ansible-<ROLENAME>.