Gitiles
Code Review Sign In
gerrit.opencord.org / platform-install / 2ab9b0066e3fcf155c34231469ae315a19f070f9 / .
tree: a330006aaf53894f12d9fc8286048576bdcebc2d [path history] [tgz]
  1. LICENSE
  2. README.md
  3. ansible.cfg
  4. cloudlab-compute.yml
  5. cloudlab-hosts
  6. cloudlab-setup.yml
  7. cord-hosts
  8. cord-post-install.yml
  9. cord-setup.yml
  10. cord.yaml
  11. enable-virt-dell.yml
  12. files/
  13. group_vars/
  14. princeton-hosts
  15. princeton-setup.yml
  16. scripts/
  17. singapore-compute.yml
  18. singapore-setup.yml
  19. stanford-compute.yml
  20. stanford-hosts
  21. stanford-setup.yml
  22. tasks/
  23. templates/
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, but it should serve as a rough guide for any XOS-managed deployment (e.g., CORD).

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

  • Set up control machine: The install playbooks in this repository are designed to be run on a separate control machine (e.g., a laptop).
    • 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 use it

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 group_vars/all. Change cloudlab: true to cloudlab: false.
  • 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

Things to note

  • 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. Again, may not be what you want. Look for the relevant Juju commands in cloudlab-setup.yaml.