Jump to: navigation, search

Difference between revisions of "XenServer/VirtualBox"

(More details on running DevStack)
(No difference)

Revision as of 12:33, 17 January 2013

Installing XenServer / XCP on Virtual Box

This is a really useful development environment when you want everything running on a single box.

The setup includes:

  • Virtual Box on your laptop or desktop
  • * Note Virtual box runs well on many platforms: Linux, MacOS X and Linux
  • XCP running in a Virtual Box VM
  • OpenStack running in a VM on XCP
  • Launching a VM on XCP using OpenStack

Install Virtual Box

You can get virtual box here: https://www.virtualbox.org/wiki/Downloads


As with any XenServer + OpenStack + DevStack deployment, it is worth getting your head strait around the networking.

While there are many options that could work, please try the recommended approach first. It will really help you understand what is possible.

The XCP VM running on Virtual box:

  • a single bridged adapter onto your primary network
  • * NAT is default, but not as useful
  • * This will make XenServer appear on your network
  • the above network is assumed to have DHCP (like that provided by a home router)

The Ubuntu VM running on XCP:

  • Always gets four interfaces
  • * eth0: private networking with the XenServer, best to ignore this one
  • * eth1: VM traffic network
  • * eth2: management network (rabbit, mysql, keystone, etc)
  • * eth3: public network (floating ip traffic, external access to APIs)

For a nice picture see the official docs: http://docs.openstack.org/folsom/openstack-compute/admin/content/introduction-to-xen.html#xenapi-deployment-architecture

Installing XCP

First download the XCP ISO onto the machine running virtual box from xen xcp 1.6 download site

Once complete you need to create a virtual box VM with:

  • cd drive attached to the XCP ISO
  • a bridged network interface onto a network (ideally with a DHCP server and an internet connection, just like most home networks)
  • enable the following motherboard options:
  • * Enable IO APIC
  • * Hardware clock in UTC
  • enable the following processor and Acceleration options:
  • * PAE, VT-x, Nested Paging
  • Add a single hard disk of at least 50 GB
  • Audio and USB can be disabled

Now you have the VM, start up the VM and you should go into the XCP installer:

  • Ensure you select "XenServer optimised" storage when prompted
  • Configure the networking as you desire, but a static address in the same subnet as your host machine is best
  • Remove the ISO from the VM's cd drive, when requested

Running DevStack on the XCP VM

If everything has gone to plan, you should now have a working XCP server in a Virtual Box VM, running on your PC. Moreover, that XCP server should be able to connect to the internet.

We are now ready to configure and run the xen tools part of DevStack. This will create an Ubuntu VM, and run stack.sh when the VM boots, and install and configure the latest OpenStack code in that VM. We now follow the instructions from the DevStack XenServer ReadMe: https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md

Getting DevStack downloaded onto XCP's Dom0

At this stage you can ssh into the XCP box. You are now on "Dom0", the XCP control VM. It is worth adding your SSH key as an authorized key, in the usual way, to make this easier. DevStack will also copy that configuration into the DevStack VM. Ideally also create a new SSH key, and authorize that too, to enable the DevStack script to access the VM it creates.

Now we can follow step 2 of the Readme:

Configuring DevStack

The tricky part of configuration is the Network configuration. Lets step through all of the example configuration options, and add a few extras that will help in this particular case.


Running DevStack

Note: if things go wrong, you may need to clean the templates by setting the following:


Using OpenStack


Changing the configuration to use XenAPI NFS

Here is a good example of how to use Cinder with XenServer in some simple deployments.


Changing some code

There is one other use for the NFS server we have just installed. We can now access the above code from your development machine, and directly edit it. Lets look at changing Nova.