OpenStack Cloud Computing Cookbook

Creating a sandbox environment using VirtualBox (or VMware Fusion) and Vagrant allows us to discover and experiment with the OpenStack services. VirtualBox gives us the ability to spin up virtual machines and networks without affecting the rest of our working environment, and is freely available at http://www.virtualbox.org for Windows, Mac OS X, and Linux. Vagrant allows us to automate this task, meaning we can spend less time creating our test environments and more time using OpenStack. This test environment can then be used for the rest of the OpenStack Cloud Computing Cookbook.

It is assumed that the computer you will be using to run your test environment in has enough processing power that has hardware virtualization support (for example, Intel VT-X and AMD-V support) with at least 8 GB RAM. Remember we’re creating a virtual machine that itself will be used to spin up virtual machines, so the more RAM you have, the better.

Getting ready

To begin with, we must download VirtualBox from http://www.virtualbox.org/ and then follow the installation procedure once this has been downloaded.

We also need to download and install Vagrant, which will be covered in the later part.

The steps throughout the book assume the underlying operating system that will be used to install OpenStack on will be Ubuntu 14.04 LTS release.

We don’t need to download a Ubuntu 14.04 ISO as we use our Vagrant environment do this for us.

How to do it…

To create our sandbox environment within VirtualBox we will use Vagrant to define a number of virtual machines that allows us to run all of the OpenStack services used in the OpenStack Cloud Computing Cookbook.

controller = Controller services (APIs + Shared Services)
network = OpenStack Network node
compute = OpenStack Compute (Nova) for running KVM instances
swift = OpenStack Object Storage (All-In-One) installation
cinder = OpenStack Block Storage node

These virtual machines will be configured with at an appropriate amount of RAM, CPU and Disk, and have a total of four network interfaces. Vagrant automatically setups an interface on our virtual machine that will NAT (Network Address Translate) traffic out, allowing our virtual machine to connect to the network outside of VirtualBox to download packages. This NAT interface is not mentioned in our Vagrantfile but will be visible on our virtual machine as eth0. A Vagrantfile, which is found in the working directory of our virtual machine sandbox environment, is a simple file that describes our virtual machines and how VirtualBox will create them. We configure our first interface for use in our OpenStack environment, which will be the host network interface of our OpenStack virtual machines (the interface a client will connect to Horizon, or use the API), a second interface will be for our private network that OpenStack Compute uses for internal communication between different OpenStack Compute hosts and a third which will be used when we look at Neutron networking as an external provider network. When these virtual machines become available after starting them up, you will see the four interfaces that are explained below:

eth0 = VirtualBox NAT
eth1 = Host Network
eth2 = Private (or Tenant) Network (host-host communication for Neutron created networks)
eth3 = Neutron External Network (when creating an externally routed Neutron network)

Carry out the following steps to create a virtual machine with Vagrant that will be used to run the OpenStack services:

1. Install VirtualBox from http://www.virtualbox.org/The book was written using VirtualBox version 4.3.18
2. Install Vagrant from http://www.vagrantup.com/The book was written using Vagrant version 1.6.5
3. Once installed, we can define our virtual machine and networking in a file called Vagrantfile. To do this, create a working directory (for example, “~/cookbook” and edit a file in here called Vagrantfile as shown in the following command snippet:

   mkdir ~/cookbook
   cd ~/cookbook
   vim Vagrantfile

4. We can now proceed to configure Vagrant by editing the ~/cookbook/Vagrantfile file with the following code:

   # -*- mode: ruby -*-
   # vi: set ft=ruby :
   # We set the last octet in IPV4 address here
   nodes = {
    'controller' => [1, 200],
    'network' => [1, 202],
    'compute' => [1, 201],
    'swift' => [1, 210],
    'cinder' => [1, 211],
   }
   
   Vagrant.configure("2") do |config| 
     # Virtualbox
     config.vm.box = "trusty64"
     config.vm.box_url = "http://cloud-images.ubuntu.com/vagrant/trusty/current/trusty-server-cloudimg-amd64-vagrant-disk1.box"
     config.vm.synced_folder ".", "/vagrant", type: "nfs"
   
     # VMware Fusion / Workstation
     config.vm.provider "vmware_fusion" do |vmware, override|
       override.vm.box = "trusty64_fusion"
       override.vm.box_url = "https://oss-binaries.phusionpassenger.com/vagrant/boxes/latest/ubuntu-14.04-amd64-vmwarefusion.box"
       override.vm.synced_folder ".", "/vagrant", type: "nfs"
   
       # Fusion Performance Hacks
       vmware.vmx["logging"] = "FALSE"
       vmware.vmx["MemTrimRate"] = "0"
       vmware.vmx["MemAllowAutoScaleDown"] = "FALSE"
       vmware.vmx["mainMem.backing"] = "swap"
       vmware.vmx["sched.mem.pshare.enable"] = "FALSE"
       vmware.vmx["snapshot.disabled"] = "TRUE"
       vmware.vmx["isolation.tools.unity.disable"] = "TRUE"
       vmware.vmx["unity.allowCompostingInGuest"] = "FALSE"
       vmware.vmx["unity.enableLaunchMenu"] = "FALSE"
       vmware.vmx["unity.showBadges"] = "FALSE"
       vmware.vmx["unity.showBorders"] = "FALSE"
       vmware.vmx["unity.wasCapable"] = "FALSE"
     end
     
     # Default is 2200..something, but port 2200 is used by forescout NAC agent.
     config.vm.usable_port_range= 2800..2900
   
     nodes.each do |prefix, (count, ip_start)|
       count.times do |i|
         hostname = "%s" % [prefix, (i+1)]
   
         config.vm.define "#{hostname}" do |box|
           box.vm.hostname = "#{hostname}.book"
           box.vm.network :private_network, ip: "172.16.0.#{ip_start+i}", :netmask => "255.255.0.0"
           box.vm.network :private_network, ip: "172.10.0.#{ip_start+i}", :netmask => "255.255.0.0" 
           box.vm.network :private_network, ip: "192.168.100.#{ip_start+i}", :netmask => "255.255.255.0"
   
           # If using Fusion
           box.vm.provider :vmware_fusion do |v|
             v.vmx["memsize"] = 1024
             if prefix == "compute" or prefix == "controller" or prefix == "swift"
               v.vmx["memsize"] = 2048
             end # if
           end # box.vm fusion
   
           # Otherwise using VirtualBox
           box.vm.provider :virtualbox do |vbox|
             # Defaults
             vbox.customize ["modifyvm", :id, "--memory", 1024]
             vbox.customize ["modifyvm", :id, "--cpus", 1]
             vbox.customize ["modifyvm", :id, "--nicpromisc3", "allow-all"]
             vbox.customize ["modifyvm", :id, "--nicpromisc4", "allow-all"]
             if prefix == "compute" or prefix == "controller" or prefix == "swift"
               vbox.customize ["modifyvm", :id, "--memory", 2048]
               vbox.customize ["modifyvm", :id, "--cpus", 2]
             end # if
           end # box.vm virtualbox
         end # config.vm.define 
       end # count.times
     end # nodes.each
   end # Vagrant.configure("2")

5. We are now ready to power on our controller node. We do this by simply running the following command:

   vagrant up

Congratulations! We have successfully created the VirtualBox virtual machines running on Ubuntu 14.04 which is able to run OpenStack services.

How it works…

What we have done is defined a number of virtual machines within VirtualBox or VMware Fusion by defining it in Vagrant. Vagrant then configures these virtual machines, based on the settings given in Vagrantfile in the directory where we want to store and run our VirtualBox or VMware Fusion virtual machines from. This file is based on Ruby syntax, but the lines are relatively self-explanatory. We have specified some of the following:

• The hostnames are called controller, network, compute, swift and cinder and have a corresponding 4th octet IP assigned to them that i is appended to the networks given further into the file.
• The VM is based on Ubuntu Trusty Tahr, an alias for Ubuntu 14.04 LTS 64-bit
• We configure some optimizations and specific configurations for VMware and VirtualBox
• The file has been written as a series of nested loops, iterating over the “nodes” array set at the top of the file.
• In each iteration, the corresponding configuration of the virtual machine is made, and then the configured virtual machine is then brought up.

We then launch this virtual machines using Vagrant with the help of the following simple command:

vagrant up

This will launch all VMs listed in the Vagrantfile.

To see the status of the virtual machines we use the following command:

vagrant status

To log into any of the machines we use the following command:

vagrant ssh controller

replace “controller” with the name of the virtual machine you want to use.