openstack/openstack-manuals
Code Issues Proposed changes

Remove use of fixed_range from docs

Browse Source 
fixed_range in nova.conf was deprecated in Grizzly and has been
removed in Havana.

Change-Id: I663ab54260ab7a6041b951598b901cf95a259df3
Closes-Bug: 1207559
This commit is contained in:
Tom Fifield 2013-09-30 19:24:07 +04:00 committed by annegentle
parent ff20a50aa2
commit b112b46611
5 changed files with 26 additions and 41 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

45
doc/admin-guide-cloud/ch_compute.xml
View File

@ -988,42 +988,29 @@ header: Date: Thu, 13 Sep 2012 20:27:36 GMT
role="italic">not</emphasis> assigned to any of
the host's network interfaces, only to the VM's
guest-side interface.</para>
<para>In any setup with flat networking, the host(-s) with
nova-network on it is (are) responsible for forwarding
traffic from the private network. Compute can
determine the NAT entries for each network when you
have <literal>fixed_range=''</literal> in your
<filename>nova.conf</filename>. Sometimes NAT is
not used, such as when fixed_range is configured with
all public IPs and a hardware router is used (one of
the HA options). Such host(-s) needs to have
traffic from the private network. Compute can determine
the NAT entries for each network, though sometimes NAT is not
used, such as when configured with all
public IPs or a hardware router is used (one of the HA
options). Such host(-s) needs to have
<literal>br100</literal> configured and physically
connected to any other nodes that are hosting VMs. You
must set the <literal>flat_network_bridge</literal>
option or create networks with the bridge parameter in
order to avoid raising an error. Compute nodes have
iptables/ebtables entries created for each project and
instance to protect against IP/MAC address spoofing
and ARP poisoning. <note>
<para>To use the new dynamic
<literal>fixed_range</literal> setup in
Grizzly, set <literal>fixed_range=''</literal>
in your <filename>nova.conf</filename>. For
backwards compatibility, Grizzly supports the
<literal>fixed_range</literal> option,
which performs the default logic from Folsom
and earlier releases.</para>
</note></para>
must set the <literal>flat_network_bridge</literal> option
or create networks with the bridge parameter in order to
avoid raising an error. Compute nodes have
iptables/ebtables entries created for each project and instance
to protect against IP/MAC address spoofing and ARP
poisoning. </para>
<note>
<para>In single-host Flat DHCP mode you <emphasis
role="italic">will</emphasis> be able to ping
VMs through their fixed IP from the nova-network
node, but you <emphasis role="italic"
>cannot</emphasis> ping them from the compute
nodes. This is expected behavior.</para>
role="italic">will</emphasis> be able to ping VMs
through their fixed IP from the nova-network node, but
you <emphasis role="italic">cannot</emphasis> ping them
from the compute nodes. This is
expected behavior.</para>
</note>
<para><emphasis role="bold">VLAN Network Mode is the
default mode</emphasis> for OpenStack Compute. In
this mode, Compute creates a VLAN and bridge for each

1
doc/common/samples/nova.conf
View File

@ -46,7 +46,6 @@ public_interface=eth0
vlan_interface=eth0
flat_network_bridge=br100
flat_interface=eth0
fixed_range=''
# NOVNC CONSOLE
novncproxy_base_url=http://192.168.206.130:6080/vnc_auto.html

4
doc/config-reference/compute/section_compute-configure-ipv6.xml
View File

@ -5,7 +5,7 @@
xmlns:ns5="http://www.w3.org/1999/xhtml"
xmlns:ns4="http://www.w3.org/2000/svg"
xmlns:ns3="http://www.w3.org/1998/Math/MathML"
xmlns:ns="http://docbook.org/ns/docbook">
xmlns:ns="http://docbook.org/ns/docbook" version="5.0">
<title>Configuring Compute to use IPv6 Addresses</title>
<para>You can configure Compute to use both IPv4 and IPv6 addresses for
communication by putting it into a IPv4/IPv6 dual stack mode. In IPv4/IPv6
@ -41,7 +41,7 @@
<para>When using the command <command>nova network-create</command> you can add a fixed range
for IPv6 addresses. You must specify public or private after the create parameter.</para>
<screen><prompt>$</prompt> <userinput>nova network-create public --fixed-range-v4 <replaceable>fixed_range</replaceable> --vlan <replaceable>vlan_id</replaceable> --vpn <replaceable>vpn_start</replaceable> --fixed-range-v6 <replaceable>fixed_range_v6</replaceable></userinput></screen>
<screen><prompt>$</prompt> <userinput>nova network-create public --fixed-range-v4 <replaceable>fixed_range_v4</replaceable> --vlan <replaceable>vlan_id</replaceable> --vpn <replaceable>vpn_start</replaceable> --fixed-range-v6 <replaceable>fixed_range_v6</replaceable></userinput></screen>
<para>You can set IPv6 global routing prefix by using the <literal>--fixed_range_v6</literal>
parameter. The default is: <literal>fd00::/48</literal>. When you use

2
doc/install-guide/section_compute-config-guest-network.xml
View File

@ -13,7 +13,7 @@
root:<screen><prompt>#</prompt> <userinput>ip link set eth0 promisc on</userinput></screen></para>
<para os="ubuntu">Set up your /etc/network/interfaces file with these settings:</para>
<itemizedlist os="ubuntu"><listitem><para>eth0: public IP, gateway</para></listitem>
<listitem><para>br100: no ports, stp off, fd 0, first address from fixed_range set in nova.conf files.</para></listitem></itemizedlist>
<listitem><para>br100: no ports, stp off, fd 0, first address from your defined network range.</para></listitem></itemizedlist>
<para os="ubuntu">Here's an Ubuntu/Debian example:</para>
<para os="ubuntu"><programlisting># The loopback network interface
auto lo

1
doc/install-guide/section_compute-minimum-configuration.xml
View File

@ -78,7 +78,6 @@
>the reference in the <citetitle>OpenStack Configuration Reference</citetitle></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>