RDOCloud-devstack

This playbook creates a nova VM in the RDOCloud and sets up a devstack environment there with the CephNFS backend. The nova VM runs CentOS 7. The playbook has been tested running on Fedora 27/Fedora 30 but should work on CentOS, indeed on any system that supports recent ansible.

Prerequisites

We assume that you have credentials to use RDOCloud and that you have set them up in ${HOME}/.config/openstack/clouds.yaml along the following lines:

$ cat ~/.config/openstack/clouds.yaml 
clouds:
    rdo-cloud:
        auth:
            auth_url: https://phx2.cloud.rdoproject.org:13000/
            project_name: <your-project-name>
            username: <your-user-name>
            password: <your-password>
        region: RegionOne
$

CentOS

The ansible playbook needs the shade library. We don't have that packaged for CentOS so install that in a virtualenv and run the playbook after activating the virtualenv:

$ virtualenv venv
New python executable in ...
Also creating executable in ...
Installing setuptools, pip, wheel...done.
$ source venv/bin/activate
(venv) $ pip install shade
...

We also need the libselinux-python library installed. Considering we will be using the virtual environment, we will need to install the libselinux-python lib in the host and then copy the binaries to the venv. Precisely,

sudo dnf install -y libselinux-python

cp -r /usr/lib64/python3.7/site-packages/selinux $VIRTUAL_ENV/lib/python3.7/site-packages
cp /usr/lib64/python3.7/site-packages/_selinux.so $VIRTUAL_ENV/lib/python3.7/site-packages

If this previous step is not done, when trying to access the CentOS 7 image in the VM you will get "Aborting, target uses selinux but python bindings (libselinux-python) aren’t installed!" error.

We install and activate this virtualenv in the same directory as the ansible playbook.

Fedora

With Fedora 30 you can skip the virtualenv used for CentOS and just

sudo dnf install -y python3-shade python3-selinux

Keys

Before you run the playbook edit copy keys.yml.sample to keys.yml and edit the latter with the paths to your public and private ssh keys:

(venv) $ cat keys.yml.sample
---
# Set the name of the key known to the OpenStack cloud.
key_name: devstack_keypair
# Set the name of the local private key file associated
# with the named key.
private_key_file: "/path/to/your/private/key"
public_key_file: "/path/to/your/public/key"

Playbooks

Now you can run the playbook:

(venv) $ ansible-playbook devstack-setup.yml

The playbook will set up an appropriate security group, keypair, and private network, as well as a cinder volume to hold your development files and a router to connect the private network to the RDOCloud public network. It boots up the Nova VM that will host the devstack environment using these. We will refer to this Nova VM as the "host VM" henceforth in order not to confuse it with Nova VMs that you may launch inside devstack itself. We are building the host VM using openstack in RDOCloud but once built we can pretty much forget about that and treat it as if it were a physical machine on a network or a virtual machine on one's laptop.

The cinder volume created for the host VM will be used to hold your development files (e.g. /opt/stack/manila). devstack environments are notoriously unstable and tearing down a stack and re-stacking often fails to produce a working environment. The cinder volume provides a good way to persist your work if you need to destroy and rebuild the host VM.

The playbook will install a stack user and /home/stack/devstack, as well as a version of /home/stack/devstack/local.conf suitable for stacking with the CephNFS back end.

Devstack

The playbook sets up /home/centos/devstack with the latest contents and a version of local.conf suitable for stacking with the CephFS NFS back end. local.conf has comments that show how to change it to deploy with the CephFS native back end.

It does not actually run devstack since you may want to customize local.conf, etc.

The playbook writes a login.sh file in the current directory that you may use to login to your devstack host VM.

To destroy your devstack host VM and start over again just run

(venv) $ ansible-playbook destroy.yml

or to blow away the cinder volume for /opt as well:

(venv) $ ansible-playbook destroy-all.yml