Go to file

Kevin Carter b59c08dd5f Update the tempest install environment

While this should be backported this purpose of this commit
is to unblock gating and provide for the always changing
requirements within tempest while also allowing us to ensure
that we are defcore complaint.

Tempest is not an integrated service within OpenStack and does
not adhere to any given package or requirement set that would
in a real work function with the rest of OpenStack. Because
tempest is intended to be a standalone system that is not
installed along side of the rest of OpenStack it general will
break and or introduce new requirements that break the services
that depend on various versions of packages as found within
global requirements. To fix this issue tempest is now being
installed within a VENV. The virtual environment will ensure
that tempest is installed in a location where it can resolve
its own dependencies without general impact to the rest of the
system.

Additionally, we removed the heat_contrib_extraroute heat
plugin from the build process because its presently
incompatible with PBR >= 0.11.0 which is related to issue
https://bugs.launchpad.net/openstack-ansible/+bug/1450733 .
However we have already built wheels in our repo which will
still allow this contributing plugin to be installed as an
integrated part of the system. Currently, we git clone heat
source onto heat_engine containers and install selected plugins
via a 'python setup.py install'.  This change removes the tasks
that do that and simply adds heat-contrib-extraroute
to heat_pip_packages so it gets installed on all heat-related
containers.  This is actually only required on the heat_engine
containers but the package is tiny and should not cause any issues
being present on the heat_api containers.

Change-Id: Ib972704084ead5748b19362b142fb161fea4a734

2015-05-06 07:46:39 -05:00

etc

Default glance swift_backend to use local swift

2015-04-30 17:38:27 +01:00

playbooks

Update the tempest install environment

2015-05-06 07:46:39 -05:00

scripts

Default glance swift_backend to use local swift

2015-04-30 17:38:27 +01:00

.gitignore

Initial Commit

2014-08-26 18:08:15 -05:00

.gitreview

Adds .gitreview file to repo

2014-12-02 17:22:12 -06:00

ansible-role-requirements.yml.example

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

CONTRIBUTING.rst

Updating CONTRIBUTING for commit messages

2015-04-06 10:38:40 -05:00

dev-requirements.txt

updated dev requirements to allow for linting python

2015-04-07 10:25:20 +01:00

development-stack.rst

Removed all rackspace related logging parts

2015-03-14 22:35:59 -05:00

LICENSE.txt

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

README.rst

Updated ansible to use the latest stable release

2015-04-08 08:29:53 +01:00

requirements.txt

Update the tempest install environment

2015-05-06 07:46:39 -05:00

README.rst

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.

- name: SuperAwesomeModule
  src: https://github.com/super-user/SuperAwesomeModule
  version: master

Run the ./scripts/bootstrap-ansible.sh script, which will install, pip, ansible 1.9.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.
Fill in your openstack_deploy/openstack_user_config.yml, openstack_deploy/user_secrets.yml and openstack_deploy/user_variables.yml files which you've just copied to your /etc/ directory.
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:

openstack-ansible setup-everything.yml

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 the lxc-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.
Inventory is generated by executing the playbooks/inventory/dynamic_inventory.py script. This is configured in the playbooks/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".

Documentation

While no os-ansible-deployment community documentation exists (yet), other than the .rst files present in this repository, comprehensive installation guides for Rackspace Private Cloud (an opinionated version of os-ansible-deployment) are available at "http://www.rackspace.com/knowledge_center/getting-started/rackspace-private-cloud".

Note:: These docs may not be up-to-date with the current release of this repository however they are still a good source of documentation.