devstack/tools/xen
Bob Ball 2634be00b8 Correcting comment for HOST_IP_IFACE
Change-Id: I4c3438dc1168401c193841976cf8ba8534b33679
Fixes: bug #1174455
2013-04-29 23:35:57 +01:00
..
files Initial commit of xen devstack support 2011-10-26 22:29:08 -07:00
scripts Enable Xen/DevStackDomU to have larger disk 2012-11-08 10:49:32 -05:00
templates Make devstack work with xcp-xapi package on Ubuntu 12.04 2012-05-22 18:12:43 +01:00
build_domU_multi.sh Multiple vpx for xen, post splitting of script 2012-02-14 15:30:34 -08:00
build_xva.sh Disable non-dhcp resolv.conf 2013-02-08 10:50:34 +00:00
devstackubuntupreseed.cfg XenAPI: run DomU on a virtual kernel 2013-03-13 09:42:58 +00:00
functions xenapi: /boot/guest should point to local SR 2013-04-03 15:33:33 +01:00
install_os_domU.sh xenapi: Extract plugin installation functions 2013-03-25 15:12:58 +00:00
mocks xenapi: /boot/guest should point to local SR 2013-04-03 15:33:33 +01:00
prepare_guest_template.sh Remove hardwired ansolabs urls 2012-11-14 12:47:17 +00:00
prepare_guest.sh Fix "sudo: sorry, you must have a tty to run sudo" 2013-01-11 09:15:30 +01:00
README.md Correcting comment for HOST_IP_IFACE 2013-04-29 23:35:57 +01:00
test_functions.sh xenapi: /boot/guest should point to local SR 2013-04-03 15:33:33 +01:00
xenrc Small Refactors 2013-03-07 18:37:31 +00:00

Getting Started With XenServer 5.6 and Devstack

The purpose of the code in this directory it to help developers bootstrap a XenServer 5.6 (or greater) + Openstack development environment. This file gives some pointers on how to get started.

Xenserver is a Type 1 hypervisor, so it needs to be installed on bare metal. The Openstack services are configured to run within a "privileged" virtual machine on the Xenserver host (called OS domU). The VM uses the XAPI toolstack to communicate with the host.

Step 1: Install Xenserver

Install XenServer 5.6+ on a clean box. You can get XenServer by signing up for an account on citrix.com, and then visiting: https://www.citrix.com/English/ss/downloads/details.asp?downloadId=2311504&productId=683148

For details on installation, see: http://wiki.openstack.org/XenServer/Install

Here are some sample Xenserver network settings for when you are just getting started (Settings like this have been used with a laptop + cheap wifi router):

  • XenServer Host IP: 192.168.1.10
  • XenServer Netmask: 255.255.255.0
  • XenServer Gateway: 192.168.1.1
  • XenServer DNS: 192.168.1.1

Step 2: Download devstack

On your XenServer host, run the following commands as root:

wget --no-check-certificate https://github.com/openstack-dev/devstack/zipball/master
unzip -o master -d ./devstack
cd devstack/*/

Step 3: Configure your localrc inside the devstack directory

Devstack uses a localrc for user-specific configuration. Note that the XENAPI_PASSWORD must be your dom0 root password. Of course, use real passwords if this machine is exposed.

cat > ./localrc <<EOF
MYSQL_PASSWORD=my_super_secret
SERVICE_TOKEN=my_super_secret
ADMIN_PASSWORD=my_super_secret
SERVICE_PASSWORD=$ADMIN_PASSWORD
RABBIT_PASSWORD=my_super_secret
# This is the password for your guest (for both stack and root users)
GUEST_PASSWORD=my_super_secret
# IMPORTANT: The following must be set to your dom0 root password!
XENAPI_PASSWORD=my_super_secret
# Do not download the usual images yet!
IMAGE_URLS=""
# Explicitly set virt driver here
VIRT_DRIVER=xenserver
# Explicitly set multi-host
MULTI_HOST=1
# Give extra time for boot
ACTIVE_TIMEOUT=45
# Host Interface, i.e. the interface on the nova vm you want to expose the
# services on. Usually eth2 (management network) or eth3 (public network) and
# not eth0 (private network with XenServer host) or eth1 (VM traffic network)
# This is also used as the interface for the Ubuntu install
# The default is eth3.
# HOST_IP_IFACE=eth3
# First time Ubuntu network install params
NETINSTALLIP="dhcp"
NAMESERVERS=""
NETMASK=""
GATEWAY=""
EOF

Step 4: Run ./install_os_domU.sh from the tools/xen directory

cd tools/xen ./install_os_domU.sh

Once this script finishes executing, log into the VM (openstack domU) that it installed and tail the run.sh.log file. You will need to wait until it run.sh has finished executing.

Step 5: Do cloudy stuff!

  • Play with horizon
  • Play with the CLI
  • Log bugs to devstack and core projects, and submit fixes!

Step 6: Run from snapshot

If you want to quicky re-run devstack from a clean state, using the same settings you used in your previous run, you can revert the DomU to the snapshot called "before_first_boot"