<commit_before><?xml version="1.0" encoding="UTF-8"?>
<section xml:id="compute-minimum-configuration-settings"
    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">
    <title>Configuring OpenStack Compute</title>
    <para>This section describes the relevant nova.conf settings for getting a minimal install
        running. Refer to the OpenStack Compute Administration Manual for guidance on more
        configuration options.</para>
    <para>In general, you can use the same <filename>nova.conf</filename> file across the controller and compute nodes.
        However, the following configuration options need to be changed on each compute host: <itemizedlist>
            <listitem>
                <para><literal>my_ip</literal></para>
            </listitem>
            <listitem>
                <para><literal>vncserver_listen</literal></para>
            </listitem>
            <listitem>
                <para><literal>vncserver_proxyclient_address</literal></para>
            </listitem>
        </itemizedlist>For the above configuration options, you must use the IP address of the
        specific compute host, not the cloud controller.<note>
            <para>In the Essex release, the <filename>nova.conf</filename> file format changed from
                flags (<literal>--name=value</literal>) to INI file format
                    (<literal>name=value</literal>). The Compute service will function properly with
                either format.</para>
            <para>The default <filename>nova.conf</filename> format for Essex packages varies by
                distribution. Fedora packages use the new INI style format, and Ubuntu 12.04
                packages use the old flag format. By convention, this guide uses the new INI style
                format.</para>
            <para>You can automatically convert a <filename>nova.conf</filename> file from flag
                format to INI format using <command>nova-manage</command>:</para>
            <screen><prompt>$</prompt> <userinput>nova-manage config convert --help</userinput>
<computeroutput>Usage: nova-manage config convert &lt;args&gt; [options]


Options:
  -h, --help        show this help message and exit
  --infile=&lt;path&gt;  old-style flagfile to convert to config
  --outfile=&lt;path&gt;  path for output file. Writes config to stdout if not
                    specified</computeroutput></screen>
        </note>
    </para>
    <para>The packages automatically do these steps for a user
        named nova, but if you are installing as another user you
        should ensure that the <filename>nova.conf</filename> file should have its
        owner set to <literal>root:nova</literal>, and mode set to <literal>0640</literal>, since the
        file contains your MySQL server’s username and password.

    </para>
    <note><para>If you are installing as another user, you should set permissions correctly.
        This packaged install ensures that the nova user belongs
        to the nova group and that the .conf file permissions are
        set, but here are the manual commands, which should be run as root:</para>
<screen>
<prompt># </prompt><userinput>groupadd nova</userinput>
<prompt># </prompt><userinput>usermod -g nova nova</userinput>
<prompt># </prompt><userinput>chown -R nova:nova /etc/nova</userinput>
<prompt># </prompt><userinput>chmod 640 /etc/nova/nova.conf</userinput>
</screen>
    </note>
    <para>The hypervisor is set by editing <filename>/etc/nova/nova.conf</filename>.
    The hypervisor defaults to <literal>kvm</literal>, but if you are
        working within a VM already, switch to <literal>qemu</literal> on the <literal>libvirt_type=</literal> line. To use Xen, refer
        to the overview in this book for where to install nova components. </para>
    <note><para>You can also configure the nova-compute service
    (and, for example  configure a hypervisor-per-compute-node) with a
    separate <literal>nova-compute.conf</literal> file and then referring to
     <literal>nova-compute.conf</literal> in the <literal>nova.conf</literal> file.
    </para></note>

    <para>Ensure the database connection defines your backend data
        store by adding a <literal>sql_connection</literal> line to <filename>nova.conf</filename>:
        <literal>sql_connection=mysql://<replaceable>[user]</replaceable>:<replaceable>[pass]</replaceable>@<replaceable>[primary IP]</replaceable>/<replaceable>[db
        name]</replaceable></literal>, such as
        <literal>sql_connection=mysql://nova:yourpassword@192.168.206.130/nova</literal>.</para>
    <para>You must change <filename>/etc/nova/api-paste.ini</filename>
        under [filter:authtoken] to set admin_tenant_name, admin_user,
        admin_password. Most distributions have variables in place in
        this file. </para>
    <para><programlisting><xi:include parse="text" href="samples/api-paste.ini"/>
</programlisting></para>
    <para>Add these settings to
            <filename>/etc/nova/nova.conf</filename> for the network
        configuration assumptions made for this installation scenario.
        You can place comments in the <filename>nova.conf</filename>
        file by entering a new line with a <literal>#</literal> sign
        at the beginning of the line. To see a listing of all possible
        configuration option settings, see <link
            xlink:href="http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html"
            >the reference in the OpenStack Compute Administration Manual</link>.
</para>
    <programlisting>
auth_strategy=keystone
network_manager=nova.network.manager.FlatDHCPManager
fixed_range=192.168.100.0/24
public_interface=eth0
flat_interface=eth0
flat_network_bridge=br100</programlisting>
   <para>Here is an example <filename>nova.conf</filename> with commented
        sections:</para>
    <para><programlisting><xi:include parse="text" href="samples/nova.conf"/>
</programlisting></para>
    <para>
        <note>
            <para>The <literal>my_ip</literal> configuration option will be different for each host,
                edit it accordingly.</para>
        </note>
    </para>
    <para>Stop the nova- services prior to running db sync, by running
        stop commands as root. Otherwise your logs show errors because
        the database has not yet been populated:</para>

        <screen os="ubuntu">
<prompt>#</prompt> <userinput>stop nova-api</userinput>
<prompt>#</prompt> <userinput>stop nova-compute</userinput>
<prompt>#</prompt> <userinput>stop nova-network</userinput>
<prompt>#</prompt> <userinput>stop nova-scheduler</userinput>
<prompt>#</prompt> <userinput>stop nova-novncproxy</userinput>
<prompt>#</prompt> <userinput>stop nova-volume</userinput>
        </screen>
    <screen os="rhel;fedora;centos">
        <prompt>$></prompt> <userinput>for svc in api objectstore compute network volume scheduler cert; do sudo service openstack-nova-$svc stop ; sudo chkconfig openstack-nova-$svc on ;  done</userinput>
    </screen>
</section>
<commit_msg>Remove ref to customizing api-paste.ini<commit_after><?xml version="1.0" encoding="UTF-8"?>
<section xml:id="compute-minimum-configuration-settings"
    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">
    <title>Configuring OpenStack Compute</title>
    <para>This section describes the relevant nova.conf settings for getting a minimal install
        running. Refer to the OpenStack Compute Administration Manual for guidance on more
        configuration options.</para>
    <para>In general, you can use the same <filename>nova.conf</filename> file across the controller and compute nodes.
        However, the following configuration options need to be changed on each compute host: <itemizedlist>
            <listitem>
                <para><literal>my_ip</literal></para>
            </listitem>
            <listitem>
                <para><literal>vncserver_listen</literal></para>
            </listitem>
            <listitem>
                <para><literal>vncserver_proxyclient_address</literal></para>
            </listitem>
        </itemizedlist>For the above configuration options, you must use the IP address of the
        specific compute host, not the cloud controller.<note>
            <para>In the Essex release, the <filename>nova.conf</filename> file format changed from
                flags (<literal>--name=value</literal>) to INI file format
                    (<literal>name=value</literal>). The Compute service will function properly with
                either format.</para>
            <para>The default <filename>nova.conf</filename> format for Essex packages varies by
                distribution. Fedora packages use the new INI style format, and Ubuntu 12.04
                packages use the old flag format. By convention, this guide uses the new INI style
                format.</para>
            <para>You can automatically convert a <filename>nova.conf</filename> file from flag
                format to INI format using <command>nova-manage</command>:</para>
            <screen><prompt>$</prompt> <userinput>nova-manage config convert --help</userinput>
<computeroutput>Usage: nova-manage config convert &lt;args&gt; [options]


Options:
  -h, --help        show this help message and exit
  --infile=&lt;path&gt;  old-style flagfile to convert to config
  --outfile=&lt;path&gt;  path for output file. Writes config to stdout if not
                    specified</computeroutput></screen>
        </note>
    </para>
    <para>The packages automatically do these steps for a user
        named nova, but if you are installing as another user you
        should ensure that the <filename>nova.conf</filename> file should have its
        owner set to <literal>root:nova</literal>, and mode set to <literal>0640</literal>, since the
        file contains your MySQL server’s username and password.

    </para>
    <note><para>If you are installing as another user, you should set permissions correctly.
        This packaged install ensures that the nova user belongs
        to the nova group and that the .conf file permissions are
        set, but here are the manual commands, which should be run as root:</para>
<screen>
<prompt># </prompt><userinput>groupadd nova</userinput>
<prompt># </prompt><userinput>usermod -g nova nova</userinput>
<prompt># </prompt><userinput>chown -R nova:nova /etc/nova</userinput>
<prompt># </prompt><userinput>chmod 640 /etc/nova/nova.conf</userinput>
</screen>
    </note>
    <para>The hypervisor is set by editing <filename>/etc/nova/nova.conf</filename>.
    The hypervisor defaults to <literal>kvm</literal>, but if you are
        working within a VM already, switch to <literal>qemu</literal> on the <literal>libvirt_type=</literal> line. To use Xen, refer
        to the overview in this book for where to install nova components. </para>
    <note><para>You can also configure the nova-compute service
    (and, for example  configure a hypervisor-per-compute-node) with a
    separate <literal>nova-compute.conf</literal> file and then referring to
     <literal>nova-compute.conf</literal> in the <literal>nova.conf</literal> file.
    </para></note>

    <para>Ensure the database connection defines your backend data
        store by adding a <literal>sql_connection</literal> line to <filename>nova.conf</filename>:
        <literal>sql_connection=mysql://<replaceable>[user]</replaceable>:<replaceable>[pass]</replaceable>@<replaceable>[primary IP]</replaceable>/<replaceable>[db
        name]</replaceable></literal>, such as
        <literal>sql_connection=mysql://nova:yourpassword@192.168.206.130/nova</literal>.</para>
    <para>Add these settings to
            <filename>/etc/nova/nova.conf</filename> for the network
        configuration assumptions made for this installation scenario.
        You can place comments in the <filename>nova.conf</filename>
        file by entering a new line with a <literal>#</literal> sign
        at the beginning of the line. To see a listing of all possible
        configuration option settings, see <link
            xlink:href="http://docs.openstack.org/trunk/openstack-compute/admin/content/compute-options-reference.html"
            >the reference in the OpenStack Compute Administration Manual</link>.
</para>
    <programlisting>
auth_strategy=keystone
network_manager=nova.network.manager.FlatDHCPManager
fixed_range=192.168.100.0/24
public_interface=eth0
flat_interface=eth0
flat_network_bridge=br100</programlisting>
   <para>Here is an example <filename>nova.conf</filename> with commented
        sections:</para>
    <para><programlisting><xi:include parse="text" href="samples/nova.conf"/>
</programlisting></para>
    <para>
        <note>
            <para>The <literal>my_ip</literal> configuration option will be different for each host,
                edit it accordingly.</para>
        </note>
    </para>
    <para>Stop the nova- services prior to running db sync, by running
        stop commands as root. Otherwise your logs show errors because
        the database has not yet been populated:</para>

        <screen os="ubuntu">
<prompt>#</prompt> <userinput>stop nova-api</userinput>
<prompt>#</prompt> <userinput>stop nova-compute</userinput>
<prompt>#</prompt> <userinput>stop nova-network</userinput>
<prompt>#</prompt> <userinput>stop nova-scheduler</userinput>
<prompt>#</prompt> <userinput>stop nova-novncproxy</userinput>
<prompt>#</prompt> <userinput>stop nova-volume</userinput>
        </screen>
    <screen os="rhel;fedora;centos">
        <prompt>$></prompt> <userinput>for svc in api objectstore compute network volume scheduler cert; do sudo service openstack-nova-$svc stop ; sudo chkconfig openstack-nova-$svc on ;  done</userinput>
    </screen>
</section>

{'fraction_non_alphanumeric': 0.11229145871952088, 'fraction_numerical': 0.007842578069299872, 'mean_word_length': 3.312019674146941, 'pattern_counts': {'":': 0, '<': 392, '<?xml version=': 2, '>': 394, 'https://': 0, 'lorem ipsum': 0, 'www.': 4, 'xml': 10}, 'pii_count': 4, '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': '1372906', 'n_tokens_mistral': 4068, 'n_tokens_neox': 3841, 'n_words': 1217}