<commit_before><?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 nova-compute service runs as
        "openstack-compute," a 32bit service directly upon the Windows
        platform with the Hyper-V role enabled. The necessary Python
        components as well as the nova-compute 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 will need to run the
            following commands</para>
        <screen os="windows">
<prompt>C:\</prompt><userinput>net stop w32time</userinput>
        </screen>
        <screen os="windows">
<prompt>C:\</prompt><userinput>w32tm /config /manualpeerlist:pool.ntp.org,0x8 /syncfromflags:MANUAL</userinput>
        </screen>
        <screen os="windows">
<prompt>C:\</prompt><userinput>net start w32time</userinput>
        </screen>
    </section>
    <section xml:id="hyper-v-virtual-switch">
    <title>Configuring 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 os="windows">
<prompt>PS C:\</prompt><userinput>$if = Get-NetIPAddress –IPv4Address 192* | Get-NetIPInterface</userinput>
    </screen>
<screen os="windows">
<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 nova-volume
        or cinder you must first make sure the Windows iSCSI initiator service is running and started automatically.</para>
    <screen os="windows">
<prompt>C:\</prompt><userinput>sc start MSiSCSI</userinput>
        </screen>
    <screen os="windows">
<prompt>C:\</prompt><userinput>sc config MSiSCSI start="auto"</userinput>
        </screen>
    </section>

<section xml:id="live-migration-hyper-v">
        <title>Configuring 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><commit_msg>IP Parameter Typo in vSwitch Configuration<commit_after><?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 nova-compute service runs as
        "openstack-compute," a 32bit service directly upon the Windows
        platform with the Hyper-V role enabled. The necessary Python
        components as well as the nova-compute 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 will need to run the
            following commands</para>
        <screen os="windows">
<prompt>C:\</prompt><userinput>net stop w32time</userinput>
        </screen>
        <screen os="windows">
<prompt>C:\</prompt><userinput>w32tm /config /manualpeerlist:pool.ntp.org,0x8 /syncfromflags:MANUAL</userinput>
        </screen>
        <screen os="windows">
<prompt>C:\</prompt><userinput>net start w32time</userinput>
        </screen>
    </section>
    <section xml:id="hyper-v-virtual-switch">
    <title>Configuring 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 os="windows">
<prompt>PS C:\</prompt><userinput>$if = Get-NetIPAddress –IPAddress 192* | Get-NetIPInterface</userinput>
    </screen>
<screen os="windows">
<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 nova-volume
        or cinder you must first make sure the Windows iSCSI initiator service is running and started automatically.</para>
    <screen os="windows">
<prompt>C:\</prompt><userinput>sc start MSiSCSI</userinput>
        </screen>
    <screen os="windows">
<prompt>C:\</prompt><userinput>sc config MSiSCSI start="auto"</userinput>
        </screen>
    </section>

<section xml:id="live-migration-hyper-v">
        <title>Configuring 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>
{'fraction_non_alphanumeric': 0.10456862941117664, 'fraction_numerical': 0.015895231430570828, 'mean_word_length': 2.786525359576079, 'pattern_counts': {'":': 0, '<': 219, '<?xml version=': 2, '>': 219, 'https://': 0, 'lorem ipsum': 0, 'www.': 4, 'xml': 20}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5543292', 'n_tokens_mistral': 2887, 'n_tokens_neox': 2658, 'n_words': 860}