Jump to: navigation, search

Difference between revisions of "XenServer/GettingStarted"

(Steps to get OpenStack running on XenServer)
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
__NOTOC__
 
<<[[TableOfContents]]()>>
 
 
 
<pre><nowiki>#!wiki caution
 
 
'''Warning'''
 
'''Warning'''
  
 
This is still a work in progress.
 
This is still a work in progress.
</nowiki></pre>
 
 
 
= Getting started with [[XenServer]] and [[OpenStack]] =
 
 
This is an opinionated guide to setting up an [[OpenStack]] Cloud using Xen/XenServer/XCP. Use this to get started quickly. It is far from the only way to setup [[OpenStack]] using Xen.
 
  
= Install Video =
+
= Getting started with XenServer and OpenStack =
  
To get and idea of how to install [[OpenStack]] on [[XenServer]] using [[DevStack]], take a look at the following video:
+
This is an opinionated guide to setting up an OpenStack Cloud using Xen/XenServer. Use this to get started quickly. It is far from the only way to setup OpenStack using Xen.
* [http://www.youtube.com/watch?v=x_-MWihUqF4&context=C45e4ee5ADvjVQa1PpcFPgMehSJPHmhv8Eqb1bMj89p0cvQ5UDNwE= Installing OpenStack on Citrix XenServer using [[DevStack]] (on [[YouTube]])].
 
  
 
= Required Hardware =
 
= Required Hardware =
Line 23: Line 11:
 
To get started, this is probably what you want:
 
To get started, this is probably what you want:
 
* Cheap switch (most home routers will do)
 
* Cheap switch (most home routers will do)
* Linux machine (preferably, running Ubuntu 11.10)
+
* Linux machine
 
* [[XenServer]] capable machine
 
* [[XenServer]] capable machine
* (optional) Windows machine to run Citrix [[XenCenter]] (the official [[XenServer]] GUI)
+
* (optional) Windows machine to run Citrix XenCenter (the official XenServer GUI)
  
 
= Planning your Deployment =
 
= Planning your Deployment =
Line 31: Line 19:
 
The most important part of planning is getting your head around the networking.
 
The most important part of planning is getting your head around the networking.
  
Take a look at the diagram in the wiki page on [[XenServer/XenXCPAndXenServer|XenServer deployment]].
+
Take a look at the diagram in the wiki page on [[XenServer/XenAndXenServer|XenServer deployment]].
  
 
It is probably best to configure your [[XenServer]] like this:
 
It is probably best to configure your [[XenServer]] like this:
* assuming two network cards
+
* assuming one network cards
* use nic0 (the bridge called xenbr0) to have management networks
+
* assuming you have your home switch/hub/router is setup as a VLAN trunk port.
 
+
* use nic0 (the bridge called xenbr0) to have the management network
(TODO: provide example xenrc file for devstack)
 
  
= Steps to get [[OpenStack]] running on [[XenServer]] =
+
= Steps to get OpenStack running on XenServer =
  
 
Here is what you need to do:
 
Here is what you need to do:
* [[XenServer/Install|Install XenServer 6.0.2]] by running the CD install
+
* [[XenServer/Install|Install XenServer]] by running the CD install
 
* [[XenServer/PostInstall|Follow the post install steps]]
 
* [[XenServer/PostInstall|Follow the post install steps]]
* [[XenServer/DevStack|Use DevStack]] to create the XVA image for the VM that will run the nova services
+
* Use DevStack by following the [https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md Readme]. It will install the XenAPI plugins and create an Ubuntu VM that runs the [[OpenStack]] code.
* Prepare [[XenServer]] with xapi plugins and vif isolation rules
+
* [[XenServer/DevStackJeOS|Speed up your devstack by caching a JeOS template]]
* Install the VM
 
  
 
= Steps to add a second compute node =
 
= Steps to add a second compute node =
  
You can use [[DevStack]] to deploy a node that only has nova-compute and nova-network, and modify the configuration so that it talks to your other node's MySQL, Rabbit, Glance, Keystone, etc. You probably want to add something like the following in your localrc file:
+
Once you have your first machine working, it is possible to add a second [[XenServer]] host to your cloud using a very similar procedure.
 +
 
 +
You need to select what service you want to run on the second node, and modify the configuration so that it talks to your other node's MySQL, Rabbit, Glance, Keystone, etc.
 +
 
 +
You probably want to add something like the following in your localrc file (assuming you chose MULTI_HOST=true on the first node):
  
  
 
<pre><nowiki>
 
<pre><nowiki>
 
MASTER_SERVER=111.111.111.111 #replace with ip of your first server
 
MASTER_SERVER=111.111.111.111 #replace with ip of your first server
ENABLED_SERVICES=n-cpu,n-net
+
ENABLED_SERVICES=n-cpu,n-net,n-api
 +
DATABASE_TYPE=mysql
 
MYSQL_HOST=$MASTER_SERVER
 
MYSQL_HOST=$MASTER_SERVER
 
RABBIT_HOST=$MASTER_SERVER
 
RABBIT_HOST=$MASTER_SERVER

Latest revision as of 09:29, 16 October 2013

Warning

This is still a work in progress.

Getting started with XenServer and OpenStack

This is an opinionated guide to setting up an OpenStack Cloud using Xen/XenServer. Use this to get started quickly. It is far from the only way to setup OpenStack using Xen.

Required Hardware

To get started, this is probably what you want:

  • Cheap switch (most home routers will do)
  • Linux machine
  • XenServer capable machine
  • (optional) Windows machine to run Citrix XenCenter (the official XenServer GUI)

Planning your Deployment

The most important part of planning is getting your head around the networking.

Take a look at the diagram in the wiki page on XenServer deployment.

It is probably best to configure your XenServer like this:

  • assuming one network cards
  • assuming you have your home switch/hub/router is setup as a VLAN trunk port.
  • use nic0 (the bridge called xenbr0) to have the management network

Steps to get OpenStack running on XenServer

Here is what you need to do:

Steps to add a second compute node

Once you have your first machine working, it is possible to add a second XenServer host to your cloud using a very similar procedure.

You need to select what service you want to run on the second node, and modify the configuration so that it talks to your other node's MySQL, Rabbit, Glance, Keystone, etc.

You probably want to add something like the following in your localrc file (assuming you chose MULTI_HOST=true on the first node):


MASTER_SERVER=111.111.111.111 #replace with ip of your first server
ENABLED_SERVICES=n-cpu,n-net,n-api
DATABASE_TYPE=mysql
MYSQL_HOST=$MASTER_SERVER
RABBIT_HOST=$MASTER_SERVER
KEYSTONE_AUTH_HOST=$MASTER_SERVER
GLANCE_HOSTPORT=$MASTER_SERVER:9292