openstack-manuals/doc/config-reference/compute/section_hypervisor_hyper-v.xml
Gauvain Pocentek 590bb27b37 update nova flags and tables
Removed docker references (the driver has been removed from nova).

Update confilcting pages including tables to use xrefs instead.

Add a rpc_all section to handle conflicts in the training-guides.

Closes-Bug: #1291138
Closes-Bug: #1292612
Change-Id: I67ad31c3913cae4c2e9e3d2ce41302717af5d839
2014-03-23 07:41:52 +01:00

390 lines
19 KiB
XML
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<?xml version="1.0" encoding="UTF-8"?>
<section xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
xml:id="hyper-v-virtualization-platform">
<?dbhtml stop-chunking?>
<title>Hyper-V virtualization platform</title>
<para>It is possible to use Hyper-V as a compute node within an OpenStack Deployment. The
<systemitem class="service">nova-compute</systemitem> service runs as "openstack-compute," a 32-bit service directly upon the Windows
platform with the Hyper-V role enabled. The necessary Python components as well as the
<systemitem class="service">nova-compute</systemitem> service are installed directly onto the Windows platform. Windows Clustering
Services are not needed for functionality within the OpenStack infrastructure. The use of
the Windows Server 2012 platform is recommend for the best experience and is the platform
for active development. The following Windows platforms have been tested as compute nodes:<itemizedlist>
<listitem>
<para><emphasis role="bold">Windows Server 2008r2</emphasis></para>
<para>Both Server and Server Core with the Hyper-V role enabled (Shared Nothing Live
migration is not supported using 2008r2)</para>
</listitem>
<listitem>
<para><emphasis role="bold">Windows Server 2012</emphasis></para>
<para>Server and Core (with the Hyper-V role enabled), and Hyper-V Server</para>
</listitem>
</itemizedlist>
</para>
<section xml:id="installation-architecture-hyper-v">
<title>Hyper-V configuration</title>
<para>The following sections discuss how to prepare the Windows Hyper-V node for operation
as an OpenStack compute node. Unless stated otherwise, any configuration information
should work for both the Windows 2008r2 and 2012 platforms.</para>
<para><emphasis role="bold">Local Storage Considerations</emphasis></para>
<para>The Hyper-V compute node needs to have ample storage for storing the virtual machine
images running on the compute nodes. You may use a single volume for all, or partition
it into an OS volume and VM volume. It is up to the individual deploying to
decide.</para>
</section>
<section xml:id="configure-ntp-hyper-v">
<title>Configure NTP</title>
<para>Network time services must be configured to ensure proper operation of the Hyper-V
compute node. To set network time on your Hyper-V host you must run the
following commands:</para>
<screen>
<prompt>C:\</prompt><userinput>net stop w32time</userinput>
</screen>
<screen>
<prompt>C:\</prompt><userinput>w32tm /config /manualpeerlist:pool.ntp.org,0x8 /syncfromflags:MANUAL</userinput>
</screen>
<screen>
<prompt>C:\</prompt><userinput>net start w32time</userinput>
</screen>
</section>
<section xml:id="hyper-v-virtual-switch">
<title>Configure Hyper-V virtual switching</title>
<para>Information regarding the Hyper-V virtual Switch can be located here: <link
xlink:href="http://technet.microsoft.com/en-us/library/hh831823.aspx"
>http://technet.microsoft.com/en-us/library/hh831823.aspx</link>
</para>
<para>To quickly enable an interface to be used as a Virtual Interface the following
PowerShell may be used:</para>
<screen>
<prompt>PS C:\</prompt><userinput>$if = Get-NetIPAddress IPAddress 192* | Get-NetIPInterface</userinput>
</screen>
<screen>
<prompt>PS C:\</prompt><userinput>New-VMSwitch -NetAdapterName $if.ifAlias -Name yourbridgename AllowManagementOS $false</userinput>
</screen>
</section>
<section xml:id="enable-iscsi-services-hyper-v">
<title>Enable iSCSI initiator service</title>
<para>To prepare the Hyper-V node to be able to attach to volumes provided by cinder
you must first make sure the Windows iSCSI initiator service is running and
started automatically.</para>
<screen>
<prompt>C:\</prompt><userinput>sc start MSiSCSI</userinput>
</screen>
<screen>
<prompt>C:\</prompt><userinput>sc config MSiSCSI start="auto"</userinput>
</screen>
</section>
<section xml:id="live-migration-hyper-v">
<title>Configure shared nothing live migration</title>
<para>Detailed information on the configuration of live migration can be found here: <link
xlink:href="http://technet.microsoft.com/en-us/library/jj134199.aspx"
>http://technet.microsoft.com/en-us/library/jj134199.aspx</link></para>
<para>The following outlines the steps of shared nothing live migration.</para>
<orderedlist>
<listitem>
<para>The target hosts ensures that live migration is
enabled and properly configured in Hyper-V.</para>
</listitem>
<listitem>
<para>The target hosts checks if the image to be
migrated requires a base VHD and pulls it from the
Image Service if not already available on the target
host.</para>
</listitem>
<listitem>
<para>The source hosts ensures that live migration is
enabled and properly configured in Hyper-V.</para>
</listitem>
<listitem>
<para>The source hosts initiates a Hyper-V live migration.</para>
</listitem>
<listitem>
<para>The source hosts communicates to the manager the outcome of the
operation.</para>
</listitem>
</orderedlist>
<para>The following two configuration options/flags are needed in order to support Hyper-V
live migration and must be added to your <filename>nova.conf</filename> on the Hyper-V
compute node:<itemizedlist>
<listitem>
<para><literal>instances_shared_storage=False</literal></para>
<para>This needed to support "shared nothing" Hyper-V live migrations. It is
used in nova/compute/manager.py</para>
</listitem>
<listitem>
<para><literal>limit_cpu_features=True</literal></para>
<para>This flag is needed to support live migration to hosts with different CPU
features. This flag is checked during instance creation in order to limit
the CPU features used by the VM.</para>
</listitem>
<listitem>
<para>
<literal>instances_path=DRIVELETTER:\PATH\TO\YOUR\INSTANCES</literal>
</para>
</listitem>
</itemizedlist></para>
<para>Additional Requirements:</para>
<itemizedlist>
<listitem>
<para>Hyper-V 2012 RC or Windows Server 2012 RC with Hyper-V role enabled</para>
</listitem>
<listitem>
<para>A Windows domain controller with the Hyper-V compute nodes as domain
members</para>
</listitem>
<listitem>
<para>The instances_path command-line option/flag needs to be the same on all
hosts.</para>
</listitem>
<listitem>
<para>The <systemitem
class="service">openstack-compute</systemitem> service
deployed with the setup must run with domain
credentials. You can set the service credentials
with:</para>
<screen>
<prompt>C:\</prompt><userinput>sc config openstack-compute obj="DOMAIN\username" password="password"</userinput></screen>
</listitem>
</itemizedlist>
<para><emphasis role="bold">How to setup live migration on Hyper-V</emphasis></para>
<para>To enable 'shared nothing live' migration, run the 3 PowerShell instructions below on
each Hyper-V host:</para>
<screen>
<prompt>PS C:\</prompt><userinput>Enable-VMMigration</userinput>
</screen>
<screen>
<prompt>PS C:\</prompt><userinput>Set-VMMigrationNetwork <replaceable>IP_ADDRESS</replaceable></userinput>
</screen>
<screen>
<prompt>PS C:\</prompt><userinput>Set-VMHost VirtualMachineMigrationAuthenticationTypeKerberos</userinput>
</screen>
<note>
<para>Please replace the IP_ADDRESS with the address of the interface which will provide
the virtual switching for nova-network.</para>
</note>
<para><emphasis role="bold">Additional Reading</emphasis></para>
<para>Here's an article that clarifies the various live migration options in Hyper-V:</para>
<para>
<link
xlink:href="http://ariessysadmin.blogspot.ro/2012/04/hyper-v-live-migration-of-windows.html"
>http://ariessysadmin.blogspot.ro/2012/04/hyper-v-live-migration-of-windows.html</link>
</para>
</section>
<section xml:id="python-requirements-hyper-v">
<title>Python Requirements</title>
<para><emphasis role="bold">Python</emphasis></para>
<para>Python 2.7.3 must be installed prior to installing the OpenStack Compute Driver on the
Hyper-V server. Download and then install the MSI for windows here:<itemizedlist>
<listitem>
<para>
<link xlink:href="http://www.python.org/ftp/python/2.7.3/python-2.7.3.msi"
>http://www.python.org/ftp/python/2.7.3/python-2.7.3.msi</link>
</para>
</listitem>
<listitem>
<para>Install the MSI accepting the default options.</para>
</listitem>
<listitem>
<para>The installation will put python in C:/python27.</para>
</listitem>
</itemizedlist>
</para>
<para><emphasis role="bold">Setuptools</emphasis></para>
<para>You will require pip to install the necessary python module dependencies. The
installer will install under the C:\python27 directory structure. Setuptools for Python
2.7 for Windows can be download from here:</para>
<para><link
xlink:href="http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11.win32-py2.7.exe#md5=57e1e64f6b7c7f1d2eddfc9746bbaf20"
> http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11.win32-py2.7.exe
</link>
</para>
<para><emphasis role="bold">Python Dependencies</emphasis></para>
<para>You must download and manually install the following packages on the Compute
node:</para>
<itemizedlist>
<listitem>
<para><emphasis role="bold">MySQL-python</emphasis></para>
<para>
<link xlink:href="http://codegood.com/download/10/"
>http://codegood.com/download/10/</link>
</para>
</listitem>
<listitem>
<para><emphasis role="bold">pywin32</emphasis></para>
<para>Download and run the installer from the following location</para>
<para>
<link
xlink:href="http://sourceforge.net/projects/pywin32/files/pywin32/Build%20217/pywin32-217.win32-py2.7.exe"
>http://sourceforge.net/projects/pywin32/files/pywin32/Build%20217/pywin32-217.win32-py2.7.exe</link>
</para>
</listitem>
<listitem>
<para><emphasis role="bold">greenlet</emphasis></para>
<para>Select the link below:</para>
<para><link xlink:href="http://www.lfd.uci.edu/~gohlke/pythonlibs/"
>http://www.lfd.uci.edu/~gohlke/pythonlibs/</link></para>
<para>You must scroll to the greenlet section for the following file:
greenlet-0.4.0.win32-py2.7.exe</para>
<para>Click on the file, to initiate the download. Once the download is complete,
run the installer.</para>
</listitem>
</itemizedlist>
<para>You must install the following Python packages through <command>easy_install</command> or <command>pip</command>. Run the
following replacing PACKAGENAME with the following packages:</para>
<screen>
<prompt>C:\</prompt><userinput>c:\Python27\Scripts\pip.exe install <replaceable>PACKAGE_NAME</replaceable></userinput>
</screen>
<itemizedlist>
<listitem>
<para>amqplib</para>
</listitem>
<listitem>
<para>anyjson</para>
</listitem>
<listitem>
<para>distribute</para>
</listitem>
<listitem>
<para>eventlet</para>
</listitem>
<listitem>
<para>httplib2</para>
</listitem>
<listitem>
<para>iso8601</para>
</listitem>
<listitem>
<para>jsonschema</para>
</listitem>
<listitem>
<para>kombu</para>
</listitem>
<listitem>
<para>netaddr</para>
</listitem>
<listitem>
<para>paste</para>
</listitem>
<listitem>
<para>paste-deploy</para>
</listitem>
<listitem>
<para>prettytable</para>
</listitem>
<listitem>
<para>python-cinderclient</para>
</listitem>
<listitem>
<para>python-glanceclient</para>
</listitem>
<listitem>
<para>python-keystoneclient</para>
</listitem>
<listitem>
<para>repoze.lru</para>
</listitem>
<listitem>
<para>routes</para>
</listitem>
<listitem>
<para>sqlalchemy</para>
</listitem>
<listitem>
<para>simplejson</para>
</listitem>
<listitem>
<para>warlock</para>
</listitem>
<listitem>
<para>webob</para>
</listitem>
<listitem>
<para>wmi</para>
</listitem>
</itemizedlist>
</section>
<section xml:id="install-nova-windows-hyper-v">
<title>Install Nova-compute</title>
<para><emphasis role="bold">Using git on Windows to retrieve source</emphasis></para>
<para>Git be used to download the necessary source code. The installer to run Git on Windows
can be downloaded here:</para>
<para>
<link
xlink:href="http://code.google.com/p/msysgit/downloads/list?q=full+installer+official+git"
>http://code.google.com/p/msysgit/downloads/list?q=full+installer+official+git</link>
</para>
<para>Download the latest installer. Once the download is complete double click the
installer and follow the prompts in the installation wizard. The default should be
acceptable for the needs of the document.</para>
<para>Once installed you may run the following to clone the Nova code.</para>
<screen>
<prompt>C:\</prompt><userinput>git.exe clone https://github.com/openstack/nova.git</userinput>
</screen>
</section>
<section xml:id="sample_nova-conf-hyper-v">
<title>Configure Nova.conf</title>
<para>The <filename>nova.conf</filename> file must be placed in
<literal>C:\etc\nova</literal> for running OpenStack on Hyper-V. Below is a sample
<filename>nova.conf</filename> for Windows:</para>
<programlisting language="ini">[DEFAULT]
verbose=true
force_raw_images=false
auth_strategy=keystone
fake_network=true
vswitch_name=openstack-br
logdir=c:\openstack\
state_path=c:\openstack\
lock_path=c:\openstack\
instances_path=e:\Hyper-V\instances
policy_file=C:\Program Files (x86)\OpenStack\nova\etc\nova\policy.json
api_paste_config=c:\openstack\nova\etc\nova\api-paste.ini
rabbit_host=<replaceable>IP_ADDRESS</replaceable>
glance_api_servers=<replaceable>IP_ADDRESS</replaceable>:9292
image_service=nova.image.glance.GlanceImageService
instances_shared_storage=false
limit_cpu_features=true
compute_driver=nova.virt.hyperv.driver.HyperVDriver
volume_api_class=nova.volume.cinder.API
[database]
connection=mysql://nova:passwd@<replaceable>IP_ADDRESS</replaceable>/nova</programlisting>
<para><xref linkend="config_table_nova_hyperv"/> contains a reference of all
options for hyper-v.</para>
</section>
<section xml:id="prepare-hyper-v-images">
<title>Prepare images for use with Hyper-V</title>
<para>Hyper-V currently supports only the VHD file format for virtual machine instances.
Detailed instructions for installing virtual machines on Hyper-V can be found
here:</para>
<para><link xlink:href="http://technet.microsoft.com/en-us/library/cc772480.aspx"
>http://technet.microsoft.com/en-us/library/cc772480.aspx</link></para>
<para>Once you have successfully created a virtual machine, you can then upload the image to
glance using the native glance-client:</para>
<screen>
<prompt>C:\</prompt><userinput>glance image-create --name="<replaceable>VM_IMAGE_NAME</replaceable>" --is-public=true --container-format=bare --disk-format=vhd</userinput>
</screen>
</section>
<section xml:id="running_compute-with-hyper-v">
<title>Run Compute with Hyper-V</title>
<para>To start the <systemitem class="service">nova-compute</systemitem> service, run this command from a console in the Windows
server:</para>
<screen>
<prompt>C:\</prompt><userinput>C:\python27\python.exe c:\openstack\nova\bin\nova-compute.py</userinput>
</screen>
</section>
<section xml:id="troubleshooting-hyper-v">
<title>Troubleshoot Hyper-V configuration</title>
<itemizedlist>
<listitem>
<para>I ran the <literal>nova-manage service list</literal> command from my
controller; however, I'm not seeing smiley faces for Hyper-V compute nodes, what
do I do?</para>
<para><emphasis role="italic">Verify that you are synchronized with a network time
source. Instructions for configuring NTP on your Hyper-V compute node are
located <link xlink:href="#configure_ntp">here</link>
</emphasis></para>
</listitem>
</itemizedlist>
</section>
</section>