Update User Guide

Change-Id: I88f26a64652580bca96089598809805d632841c7
This commit is contained in:
John Hua 2015-09-25 18:14:54 +08:00 committed by Bob Ball
parent aca5fb9bf7
commit 8acf041d04
5 changed files with 778 additions and 212 deletions

View File

@ -6,6 +6,19 @@ provided by Citrix. This plugin provides a new Release definition in
Mirantis OpenStack to allow easy installation of production
environments based on XenServer with Fuel.
XenServer is freely available from `xenserver.org
<http://xenserver.org/open-source-virtualization-download.html>`_ and
can also be downloaded directly from `citrix.com
<http://www.citrix.com/downloads/xenserver.html>`_ if you have a My
Citrix account.
Documentation for XenServer can be found on `docs.vmd.citrix.com
<http://docs.vmd.citrix.com/XenServer/6.5.0/1.0/en_gb/>`_ and for how
XenServer works within OpenStack at docs.openstack.org in the
`OpenStack Configuration Reference
<http://docs.openstack.org/juno/config-reference/content/introduction-to-xen.html>`_
guide
Requirements
------------

View File

@ -5,6 +5,40 @@ Once the Fuel XenServer plugin has been installed (following
`Installation Guide`_), you can create *OpenStack* environments that
use XenServer as the underlying hypervisor
Prepare infrastructure
----------------------
1. Everyone will have different infrastructure requirements. The additional requirements placed by XenServer are:
- Compute nodes must be run as a Virtual Machine, with one VM per XenServer hypervisor
- Ensure that the connectivity through to this virtual machine is the same as all other service nodes, as with standard Mirantis OpenStack setups
- An internal network is added by the instructions below, to provide communication between the host and the compute VM.
- Other service nodes (e.g. storage node) can also be created as virtual machines, but this is not required
2. Download and install XenServer 6.5 with SP1 and HIMN tool, a XenServer plugin, as install guide mentioned. Use it for future VM creation and network configuration.
3. While many networking setups are expected to work, the following setup is known to work:
- Physical machines with two ethernet devices:
- eth0 / “Access network”: Used to access the XenServer hosts and Fuel Master during setup.
- eth1 / “VLAN network”: Carries all traffic during setup + use of OpenStack. Untagged packets are tagged at the switch to ensure isolation from eth0.
- Two virtual networks
- VLAN 'A' on eth1 / “PXE network”: Used for node bootstrapping.
- VLAN 'B' on eth1 / "br100": Used to give connectivity between VM and router.
4. To simplify the setup, the fuel master can also be installed on the XenServer hosts (so XenServer hosts can fully control the network setup), but this is not required.
One example deployment, shown below, makes use of VLAN 19 for the "PXE network" and provides an isolated network for eth1 by tagging any untagged traffic at the switch with VLAN 237
.. image:: images/topology00.png
:width: 80%
Select Environment
------------------

BIN
doc/images/topology00.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 25 KiB

File diff suppressed because one or more lines are too long

View File

@ -13,3 +13,13 @@ Sections
.. include:: content/installation.rst
.. include:: content/guide.rst
Further reading
===============
Here are some of the resources available to learn more about Xen:
- Citrix XenServer official documentation: http://docs.vmd.citrix.com/XenServer
- What is Xen? by Xen.org: http://xen.org/files/Marketing/WhatisXen.pdf
- Xen Hypervisor project: http://www.xenproject.org/developers/teams/hypervisor.html
- Xapi project: http://www.xenproject.org/developers/teams/xapi.html
- Further XenServer and OpenStack information: http://wiki.openstack.org/XenServer