openstack/openstack-manuals
Code Issues Proposed changes

Cleaned up module002-ch005-floating-ips

Browse Source 
added transition word "the"
changed store to stored
routersis added space between routers and is

Change-Id: Ib51e6639340d18093ed11f123f99c8212e4f2019
This commit is contained in:
Shilla Saebi 2014-01-17 13:22:31 -05:00
parent ccbdd38148
commit f87d0fb634
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/training-guides/module002-ch005-floating-ips.xml
View File

@ -36,11 +36,11 @@
instance</para>
</listitem>
</itemizedlist>
<para>Just as shown by above figure, we will have
<para>Just as shown by the above figure, we will have
nova-network-api to support nova client floating
commands. nova-network-api will invoke neutron cli lib
to interactive with neutron server via API. The data
about floating IPs will be store in to neutron DB.
about floating IPs will be stored in to neutron DB.
Neutron Agent, which is running on compute host will
enforce the floating IP.</para>
<para><guilabel>Multiple Floating
@ -57,7 +57,7 @@
network that the L3 agent handles. You can run
multiple L3 agent instances on one host.</para>
<para>In addition, when you run multiple L3 agents, make
sure that handle_internal_only_routersis set to
sure that handle_internal_only_routers is set to
Trueonly for one L3 agent in an OpenStack Networking
deployment and set to Falsefor all other L3 agents.
Since the default value of this parameter is True, you