From f87d0fb634a9e88d38225dfe03681b7d83602a3d Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Fri, 17 Jan 2014 13:22:31 -0500 Subject: [PATCH] Cleaned up module002-ch005-floating-ips added transition word "the" changed store to stored routersis added space between routers and is Change-Id: Ib51e6639340d18093ed11f123f99c8212e4f2019 --- doc/training-guides/module002-ch005-floating-ips.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/training-guides/module002-ch005-floating-ips.xml b/doc/training-guides/module002-ch005-floating-ips.xml index 012fc401ea..3276c852fe 100644 --- a/doc/training-guides/module002-ch005-floating-ips.xml +++ b/doc/training-guides/module002-ch005-floating-ips.xml @@ -36,11 +36,11 @@ instance - Just as shown by above figure, we will have + 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. Multiple Floating @@ -57,7 +57,7 @@ network that the L3 agent handles. You can run multiple L3 agent instances on one host. 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