Building the development setup

To start the installation process, execute the Ansible bootstrap script. This script will download and install the correct Ansible version. It also creates a wrapper script around ansible-playbook called openstack-ansible that always loads the OpenStack user variable files:

# scripts/bootstrap-ansible.sh

The next step is to configure the system for the All-In-One setup. Executing the following script does this:

# scripts/bootstrap-aio.sh

This script does the following tasks:

• Applies Ansible roles to install the basic software requirements, such as openssh and pip
• Applies the bootstrap_host role to check the hard disk and swap space
• Creates various loopback volumes for use with Cinder, Swift, and Nova
• Prepares networking

Finally, run the playbooks to bring up the AIO development environment:

# scripts/run-playbooks.sh

This script will execute the following tasks:

• Create the LXC containers
• Apply security hardening to the host
• Reinitiate the network bridges
• Install the infrastructure services such as MySQL, RabbitMQ, and Memcached
• Finally, it installs the various OpenStack services

Running the playbooks takes a long time to build the containers and start the OpenStack services. Once finished, you will have all the OpenStack services running in their private containers. The following command line output shows the AIO server deployed using containerized OpenStack services:

You can use the lxc-ls command to list the service containers on the development machine:

# lxc-ls --fancy

Use the lxc-attach command to connect to any container, as shown here:

# lxc-attach --name <name_of_container>

Use the name of the container from the output of lxc-ls to attach to the container. LXC commands can be used to start and stop the service containers.

The AIO environment brings a MySQL cluster. Take special care when starting the MySQL cluster if the development machine is rebooted. Details of operating the AIO environment are available in the OpenStack Ansible QuickStart guide at http://docs.openstack.org/developer/openstack-ansible/developer-docs/quickstart-aio.html.

Although our setup is not considered a ready staging environment yet, it is important to consider forking the host files in Ansible into more units with different OpenStack nodes. The OSA deployment empowers the isolation of the various OpenStack services and keeps maintaining each service separately easy and safe. The current development environment is crucial to run functional tests of the OpenStack playbooks and generate a first feedback about the consistency of the Ansible code. More iterations will be performed during subsequent phases before pushing to staging and then deploying into production by considering a multinode setup running in a containerized environment.