Document supporting external gateways in VLAN mode.

This feature was introduced in https://review.openstack.org/10468
and has been merged into Nova.

Patchset fixes the build of the bk-compute-adminguide.xml file
and rebases against master.

Change-Id: Iabe8d89846a74f08bf16e0c0f2b8efb5eee35b28
This commit is contained in:
Lorin Hochstein 2012-07-29 20:32:00 -04:00 committed by annegentle
parent 303af1019d
commit 491a82a151
3 changed files with 32 additions and 12 deletions

View File

@ -26,7 +26,6 @@
support in OpenStack, but KVM will provide better performance. To enable
QEMU:<programlisting>compute_driver=libvirt.LibvirtDriver
libvirt_type=qemu</programlisting></para>
<para>
For some operations you may also have to install the <command>guestmount</command> utility:</para>
<screen os="ubuntu">
@ -35,9 +34,8 @@ libvirt_type=qemu</programlisting></para>
<screen os="rhel;fedora;centos">
<prompt>$></prompt> <userinput>sudo yum install libguestfs-tools</userinput>
</screen>
<para>The QEMU hypervisor supports the following virtual machine image formats:</para><itemizedlist>
<para>The QEMU hypervisor supports the following virtual machine image formats:</para>
<itemizedlist>
<listitem>
<para>Raw</para>
</listitem>

View File

@ -26,7 +26,7 @@
</copyright>
<releaseinfo>trunk</releaseinfo>
<productname>OpenStack Compute</productname>
<pubdate>2012-05-03</pubdate>
<pubdate>2012-08-01</pubdate>
<legalnotice role="apache2">
<annotation>
<remark>Copyright details are filled in by the template.</remark>
@ -43,6 +43,16 @@
managing, and understanding the software that runs OpenStack Compute. </para>
</abstract>
<revhistory>
<revision>
<date>2012-08-01</date>
<revdescription>
<itemizedlist spacing="compact">
<listitem>
<para>Adds QEMU information, XenAPI information, EC2 API configuration, rootwrap configuration, updates to cloudpipe information, dnsmasq information, expands network troubleshooting, and other various doc improvements.</para>
</listitem>
</itemizedlist>
</revdescription>
</revision>
<revision>
<date>2012-05-03</date>
<revdescription>

View File

@ -1517,8 +1517,25 @@ enabled_apis=ec2,osapi_compute,osapi_volume,metadata</programlisting></para>
<listitem>
<para>Create a <systemitem class="service">dnsmasq</systemitem>
configuration file (e.g., <filename>/etc/dnsmasq-nova.conf</filename>)
that contains the IP address of the external gateway using the following
syntax:<programlisting>dhcp-option=3,<replaceable>&lt;ip of gateway></replaceable></programlisting></para>
that contains the IP address of the external gateway. If running in
FlatDHCP mode, assuming the IP address of the hardware gateway was
172.16.100.1, the file would contain the
line:<programlisting>dhcp-option=option:router,<replaceable>172.16.100.1</replaceable></programlisting></para>
<para>If running in VLAN mode, a separate router must be specified for each
network. The networks are identified by the <literal>--label</literal>
argument when calling <command>nova-manage network create</command> to
create the networks as documented in the <link
linkend="configuring-vlan-networking">Configuring VLAN Networking
subsection</link>. Assuming you have three VLANs, that are labeled
<literal>red</literal>, <literal>green</literal>, and
<literal>blue</literal>, with corresponding hardware routers at
<literal>172.16.100.1</literal>, <literal>172.16.101.1</literal> and
<literal>172.16.102.1</literal>, the <systemitem class="service"
>dnsmasq</systemitem>configuration file (e.g.,
<filename>/etc/dnsmasq-nova.conf</filename>) would contain the
following:<programlisting>dhcp-option=tag:'red',option:router,172.16.100.1
dhcp-option=tag:'green',option:router,172.16.101.1
dhcp-option=tag:'blue',option:router,172.16.102.1</programlisting></para>
</listitem>
<listitem>
<para>Edit <filename>/etc/nova/nova.conf</filename> to specify the location
@ -1548,11 +1565,6 @@ enabled_apis=ec2,osapi_compute,osapi_volume,metadata</programlisting></para>
for virtual machines is routable.</para>
</listitem>
</orderedlist></para>
<warning>
<para>The hardware gateway option is not available when running in VLAN mode, as it
can only be used to specify a single gateway for all instances, and VLAN mode
requires a separate gateway for each network.</para>
</warning>
</simplesect>
</section>