From 0b2e9c8961f9ae4046d8c990dc11612e198a97a8 Mon Sep 17 00:00:00 2001 From: Shilla Saebi Date: Sat, 6 Sep 2014 15:45:33 -0400 Subject: [PATCH] changes to section_run)neutron_l3_agent added a , removed thanks and added due removed But and kept There, capitalized removed spaces between Active/Passive, Active/Active Change-Id: I0f5774241bcdad50fa80fa1b8a0532f013c1f53b --- .../ha_aa_network/section_run_neutron_l3_agent.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml b/doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml index ed7fa5b2d8..e5721fc0e4 100644 --- a/doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml +++ b/doc/high-availability-guide/ha_aa_network/section_run_neutron_l3_agent.xml @@ -6,10 +6,10 @@ Run neutron L3 agent - The neutron L3 agent is scalable thanks to the scheduler + The neutron L3 agent is scalable, due to the scheduler that allows distribution of virtual routers across multiple nodes. -But there is no native feature to make these routers highly available. -At this time, the Active / Passive solution exists to run the Neutron L3 -agent in failover mode with Pacemaker. See the Active / Passive +There is no native feature to make these routers highly available. +At this time, the active/passive solution exists to run the Neutron L3 +agent in failover mode with Pacemaker. See the active/passive section of this guide.