e09216aa4e
In order to demonstrate that OSA can be built without any containers, and to validate on a continuous basis that it still works, a new scenario is implemented to test it. As part of this, the following is done: 1. An example environment override file is added which sets all the containers with 'is_metal: true' which disables the container creation. 2. As haproxy is not used for the scenario on an AIO, the haproxy environment configuration is broken out from openstack_user_config into its own conf.d file and the implementation of it into user space is added to all other scenarios. 3. To ensure that the pip lockdown configuration is not implemented by the pip install role when the repo server doesn't exist yet, we ensure that the var is set in the playbook that does the validation. 4. To ensure that rabbitmq is able to correctly start up we implement the same host name on the host as we do in the inventory. Without this rabbitmq fails. In order to do this successfully with ansible, the dbus package must be installed on the host, so it is added as part of the AIO bootstrapping. 5. The workflow for a deployment needs no changes because when the lxc-related playbooks execute, they simply skip over because the lxc-related groups are empty. Depends-On: https://review.openstack.org/542307 Change-Id: I67199e1f35c91c4e2c9973e011e856c6ac3fb086 |
||
---|---|---|
deploy-guide/source | ||
doc | ||
etc | ||
inventory | ||
osa_toolkit | ||
playbooks | ||
releasenotes | ||
scripts | ||
tests | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
ansible-role-requirements.yml | ||
ansible-role-requirements.yml.example | ||
bindep.txt | ||
global-requirement-pins.txt | ||
LICENSE.txt | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
Vagrantfile |
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>.