Difference between revisions of "XenServer/DevStack"
m (Text replace - "__NOTOC__" to "") |
m (Text replace - "DevStack" to "DevStack") |
||
Line 2: | Line 2: | ||
<<[[TableOfContents]](2)>> | <<[[TableOfContents]](2)>> | ||
− | = | + | = DevStack and [[XenServer]] = |
[http://devstack.org DevStack] is a great way to get started with [[OpenStack]]. [[XenServer]] and XCP are great ways to use the Xen hypervisor that powers some of the world's largest clouds. | [http://devstack.org DevStack] is a great way to get started with [[OpenStack]]. [[XenServer]] and XCP are great ways to use the Xen hypervisor that powers some of the world's largest clouds. | ||
Line 15: | Line 15: | ||
Take a look at this video: | Take a look at this video: | ||
− | * [http://www.youtube.com/watch?v=x_-MWihUqF4 Installing OpenStack on Citrix XenServer using | + | * [http://www.youtube.com/watch?v=x_-MWihUqF4 Installing OpenStack on Citrix XenServer using DevStack (on [[YouTube]])] |
− | == Installing | + | == Installing DevStack by generating an Ubuntu xva == |
Again there are two options: | Again there are two options: | ||
− | * Build the XVA using | + | * Build the XVA using DevStack in Dom0 (note: default [[XenServer]] 6.0 install will not leave enough free space) |
* Build the XVA on different machine, then copy the XVA to the [[XenServer]] | * Build the XVA on different machine, then copy the XVA to the [[XenServer]] | ||
Line 26: | Line 26: | ||
* [[XenServer/Install|Install XenServer]] | * [[XenServer/Install|Install XenServer]] | ||
* prepare_dom0.sh - installs git in Dom0 | * prepare_dom0.sh - installs git in Dom0 | ||
− | * Write a | + | * Write a DevStack config file, that matches your setup |
* [prepare_guest.sh - optional - if it is not run, next script pulls image from web] | * [prepare_guest.sh - optional - if it is not run, next script pulls image from web] | ||
− | * build_xva.sh - create the | + | * build_xva.sh - create the DevStack VM image (in XVA format) |
* build_domU.sh - install xapi plugins, and Open vSwitch isolation rules, and xva image | * build_domU.sh - install xapi plugins, and Open vSwitch isolation rules, and xva image | ||
* On boot the XVA image runs stack.sh | * On boot the XVA image runs stack.sh | ||
Line 37: | Line 37: | ||
(More details coming soon...) | (More details coming soon...) | ||
− | == Installing | + | == Installing DevStack on your own Ubuntu paravirtualized VM == |
This is not really heavily tested, you are probably best looking at the approach below. | This is not really heavily tested, you are probably best looking at the approach below. |
Revision as of 23:32, 17 February 2013
<<TableOfContents(2)>>
Contents
DevStack and XenServer
DevStack is a great way to get started with OpenStack. XenServer and XCP are great ways to use the Xen hypervisor that powers some of the world's largest clouds.
To get started, you first you need to install XenServer or XCP on a physical machine.
Then there are two possible ways forward:
- Create your own Ubuntu PV VM on your XenServer, set VIRT_DRIVER=xenserver, and then run stack.sh
- Use tools/xen to build an Ubuntu PV VM for you
Video Guide
Take a look at this video:
Installing DevStack by generating an Ubuntu xva
Again there are two options:
- Build the XVA using DevStack in Dom0 (note: default XenServer 6.0 install will not leave enough free space)
- Build the XVA on different machine, then copy the XVA to the XenServer
The basic process is:
- Install XenServer
- prepare_dom0.sh - installs git in Dom0
- Write a DevStack config file, that matches your setup
- [prepare_guest.sh - optional - if it is not run, next script pulls image from web]
- build_xva.sh - create the DevStack VM image (in XVA format)
- build_domU.sh - install xapi plugins, and Open vSwitch isolation rules, and xva image
- On boot the XVA image runs stack.sh
You can read more about this in the readme:
(More details coming soon...)
Installing DevStack on your own Ubuntu paravirtualized VM
This is not really heavily tested, you are probably best looking at the approach below.
Please note:
- The VM must be running in PV mode (/sys/hypervisor/uuid is needed)
- It must be on the same hypervisor as the one you are managing
Useful Notes
Please note: