commit	418b982e7a9d2fd4be9fac7137b59c51ddc04e12	[log] [tgz]
author	Andy Bavier <acb@cs.princeton.edu>	Wed Mar 02 14:38:38 2016 -0500
committer	Andy Bavier <acb@cs.princeton.edu>	Wed Mar 02 14:38:38 2016 -0500
tree	ed87a7be28c0a0b739fd22c37478b0f0ef644e2e
parent	9114d89c772ecd16ccf1d81ab6aa1ae06830714b [diff]

tree: ed87a7be28c0a0b739fd22c37478b0f0ef644e2e

README.md

openstack-cluster-setup

This repository contains Ansible playbooks for installing and configuring an OpenStack Kilo cluster for use with XOS. This is how we build clusters for OpenCloud, and is the method of installing a CORD development POD as well.

All of the OpenStack controller services are installed in VMs on a single "head node" and connected by an isolated private network. Juju is used to install and configure the OpenStack services.

Prerequisites (OpenCloud and CORD)

Set up control machine: The install playbooks in this repository can either run on a separate control machine (e.g., a laptop) or on the cluster head node. Either way:
- Install a recent version of Ansible (Ansible 1.9.x on Mac OS X or Ubuntu should work).
- Be able to login to all of the cluster servers from the control machine using SSH.
Set up servers: One server in the cluster will be the "head" node, running the OpenStack services. The rest will be "compute" nodes.
Install Ubuntu 14.04 LTS on all servers.
The user account used to login from the control machine must have sudo access.
Each server should have a single active NIC (preferably eth0) with connectivity to the Internet.

How to install a CORD POD

The CORD POD install procedure uses the "head node" of the cluster as the control machine for the install. As mentioned above, install Ansible on the head node and check out this repository.

The playbooks assume that a bridge called mgmtbr on the head node is connected to the management network. Note that also there must be a DHCP server on the management network that:

hands out IP addresses to VMs connected to mgmtbr
resolves VM names to IP addresses
is configured as a resolver on the head and compute nodes

If you need to set up dnsmasq to do this, take a look at this example configuration. Then follow these steps:

Run the bootstrap.sh script to install Ansible and set up keys for login via localhost
Edit cord-hosts with the DNS names of your compute nodes, and update the ansible_ssh_user variable appropriately. Before proceeding, these commands needs to work on the head node:

$ ansible -i cord-hosts head -m ping
$ ansible -i cord-hosts compute -m ping

Run:

ansible-playbook -i cord-hosts cord-setup.yml

After the playbook finishes, wait for the OpenStack services to come up. You can check on their progress using juju status --format=tabular
Once the services are up, you can use the admin-openrc.sh credentials in the home directory to interact with OpenStack. You can SSH to any VM using ssh ubuntu@<vm-name>

This will bring up various OpenStack services, including Neutron with the VTN plugin. It will also create two VMs called xos and onos-cord and prep them. Configuring and running XOS and ONOS in these VMs is beyond the scope of this README.

NOTE: The install process only brings up a single nova-compute node. To bring up more nodes as compute nodes, perform these steps on the head node:

$ juju add-machine ssh:<user>@<compute-host>
$ juju add-unit nova-compute --to <juju-machine-id>

Refer to the Juju documentation for more information.

Caveats

The goal is to configure HA for the OpenStack services, but this is not yet implemented.

How to install a single-node CORD test environment on CloudLab

The process for setting up a CORD test environment on CloudLab is similar (but not identical) to the one for setting up a CORD POD above.

Start a CloudLab experiment using profile OnePC-Ubuntu14.04.3
Run the bootstrap.sh script to install Ansible and set up keys for login via localhost
Run:

ansible-playbook -i cord-test-hosts cord-setup.yml

This will bring up various OpenStack services, including Neutron with the VTN plugin. It will also create two VMs called xos and onos-cord and prep them. It creates a single nova-compute node running inside a VM.

It should be possible to use this method on any server running Ubuntu 14.04, as long as it has sufficient CPU cores and disk space.

NOTE: Currently VMs can be created using this configuration and logged into over the VTN-supplied management network. However without the CORD fabric they don't have external connectivity, and as a result a vSG cannot be spun up. A workaround for this issue should be in place shortly.

How to install an OpenCloud cluster

Once the prerequisites are satisfied, here are the basic steps for installing a new OpenCloud cluster named 'foo':

Create foo-setup.yml and foo-compute.yml files using cloudlab-setup.yml and cloudlab-compute.yml as templates. Create a foo-hosts file with the DNS names of your nodes based on cloudlab-hosts.
If you are not installing on CloudLab, edit foo-hosts and add cloudlab=False under [all:vars].
If you are installing a cluster for inclusion in the public OpenCloud, change mgmt_net_prefix in foo-setup.yml to be unique across all OpenCloud clusters.
To set up Juju, use it to install the OpenStack services on the head node, and prep the compute nodes, run on the head node:

$ ansible-playbook -i foo-hosts foo-setup.yaml

Log into the head node. For each compute node, put it under control of Juju, e.g.:

$ juju add-machine ssh:ubuntu@compute-node

To install the nova-compute service on the compute nodes that were added to Juju, run on the control machine:

$ ansible-playbook -i foo-hosts foo-compute.yaml

Caveats

The installation configures port forwarding so that the OpenStack services can be accessed from outside the private network. Some OpenCloud-specific firewalling is also introduced, which will likely require modification for other setups. See: files/etc/libvirt/hooks/qemu.
By default the compute nodes are controlled and updated automatically using ansible-pull from this repo. You may want to change this.
All of the service interfaces are configured to use SSL because that's what OpenCloud uses in production. To turn this off, look for the relevant Juju commands in cloudlab-setup.yaml.