Differences between revisions 1 and 2
Revision 1 as of 2013-03-30 14:01:19
Size: 701
Editor: DanielPocock
Comment:
Revision 2 as of 2013-03-30 14:38:25
Size: 1376
Editor: DanielPocock
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 9: Line 8:
 * Xen XCP is a way of managing the bare metal. It also provides a way to run virtual machines (referred to as domU instances in the Xen docs) that are not related to OpenStack  * Xen XCP is a way of managing the bare metal. It also provides a way to run virtual machines (referred to as domU instances in the Xen docs) that are not related to OpenStack.
Line 11: Line 10:

== How to go about it ==

 * Understand XCP by itself
 * Understand the architecture of OpenStack + XCP
  * https://wiki.openstack.org/wiki/XenServer/XenXCPAndXenServer
 * Set up a physical host with wheezy, and then install the Xen XCP packages
 * Do the OpenStack post-Xen-install steps
  * https://wiki.openstack.org/wiki/XenServer/PostInstall
 * Install a Xen domU host running wheezy (to be the OpenStack control VM)
  * This could be done using DevStack, https://github.com/openstack-dev/devstack/blob/master/tools/xen/README.md
  * Debian-specific instructions coming soon

== References ==

 * https://wiki.openstack.org/wiki/XenServer/GettingStarted

About this guide

This page eventually aims to provide an easy step-by-step guide to set up an XCP and OpenStack cloud with a stable release of Debian. That is not possible yet, but we do aim to get together useful resources to help you do things the Debian way.

Overview

  • Xen XCP is a way of managing the bare metal. It also provides a way to run virtual machines (referred to as domU instances in the Xen docs) that are not related to OpenStack.

  • OpenStack provides a cookie-cutter mechanism to run scalable, distributed server instances on-demand. It's ability to duplicate images and manage storage for distributed applications goes beyond the capabilities of XCP.

How to go about it

References