
This change implements the change to allow testr to run in serial which should resolve most issues with tempest on a resource constrained host. The problem that is being resolved here is that testr will, by default, run in multi-threaded and has a relitively high probability to result in a 503. This primarily impacts the gate jobs as they are built on a hosts with 4 CPUs and 8GB of ram. By default if the tempest script is run, testr will run multi-threaded. However, if the environment variable RUN_TEMPEST_OPTS is set to '--serial' then it will run in serial. This is done for the gate-check-commit script so that the change only affects the AIO gate check. An additional environment variable TESTR_OPTS is added for further flexibility. Co-Authored-By: Jesse Pretorius <jesse.pretorius@rackspace.co.uk> Closes-Bug: #1428847 Change-Id: I8c7ac72ef46ae3f3af3d3503081bec0cbe7276e9
OpenStack Ansible Deployment
- date
-
2015-02-02 22:00
- tags
-
lxc, openstack, cloud, ansible
- category
-
*nix
Playbooks
There are several playbooks within that will setup hosts for use in OpenStack Cloud. The playbooks will enable LXC on hosts and provides the ability to deploy LXC containers for use within openstack.
- Plays:
-
setup-hosts.yml
Performs host setup for use with LXC in the OpenStack hosts.setup-infrastructure.yml
Performs all of the setup for all infrastructure components.setup-openstack.yml
Performs all of the setup for all of the OpenStack components.
- If you dont want to run plays individually you can simply run
setup-everything.yml
which will perform all of the setup and installation for you.
- Basic Setup:
-
- If you have any roles that you'd like to have pulled in that are
outside the scope and or replace modules within this repository please
add them to the
ansible-role-requirements.yml
file. In this file you will want to fill in the details for the role you want to pull in using standard ansible galaxy format.
- Run the
./scripts/os-ansible-bootstrap.sh
script, which will install, pip, ansible 1.8.x, all of the required python packages, and bring in any third part ansible roles that you may want to add to the deployment. - Copy the
etc/openstack_deploy
directory to/etc/openstack_deploy
or if you are executing all of this as an unprivileged user you can add theopenstack_deploy
bits into your home directory as${HOME}/.openstack_deploy
. - Fill in your
openstack_deploy/openstack_user_config.yml
,openstack_deploy/user_secrets.yml
andopenstack_deploy/user_variables.yml
files which you've just copied to your/etc/
directory or your${HOME}
folder. - Generate all of your random passwords executing
scripts/pw-token-gen.py --file /etc/openstack_deploy/user_secrets.yml
. - Accomplish all of the host networking that you want to use within
the deployment. See the
etc/network
directory in this repository for an example network setup. - When ready change to the
playbooks/
directory and execute your desired plays. IE:
- If you have any roles that you'd like to have pulled in that are
outside the scope and or replace modules within this repository please
add them to the
Notes
- If you run the
./scripts/bootstrap-ansible.sh
script a wrapper script will be added to your system that wraps the ansible-playbook command to simplify the arguments required to run openstack ansible plays. The name of the wrapper script is openstack-ansible. - The lxc network is created within the lxcbr0 interface.
This supports both NAT networks as well as more traditional networking.
If NAT is enabled (default) the IPtables rules will be created along
with the interface as a post-up processes. If you ever need to recreate
the rules and or restart the dnsmask process you can bounce the
interface IE:
ifdown lxcb0; ifup lxcbr0
or you can use thelxc-system-manage
command. - The tool
lxc-system-manage
is available on all lxc hosts and can assist in recreating parts of the LXC system whenever its needed. - Our repository uses a custom LXC
module which adds
lxc:
support to Ansible. The module within this repository is presently pending in upstream ansible at "https://github.com/ansible/ansible-modules-extras/pull/123". - Inventory is generated by executing the
playbooks/inventory/dynamic_inventory.py
script. This is configured in theplaybooks/ansible.cfg
file.
Bugs and Blueprints
Everything we do is in launchpad and gerrit. If you'd like to raise a bug, feature request, or are looking for ways to contribute please go to "https://launchpad.net/openstack-ansible".
Official Documentation
Comprehensive installation guides, including FAQs and release notes, can be found at "http://docs.rackspace.com/rpc/api/v9/bk-rpc-installation/content/rpc-common-front.html" < Note that these docs may not be up-to-date with the current release of this repository however they are still a good source of documentation.