openstack/openstack-manuals
Code Issues Proposed changes

cleanup neutron_per-tenant-routers-with-private-networks

Browse Source 
added the before operating system
removed plural for operating system
added the before operating system
added the before floating IP
added the before external network
added the before floating IP
removed extra the and added the

Change-Id: I8ff2f20ef3db982c57aa9f5e40ce3e301f89c089
This commit is contained in:
Shilla Saebi 2014-02-18 19:07:41 -05:00
parent 8d94af1f02
commit 42de359d7a
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/install-guide/section_neutron-per-tenant-routers-with-private-networks.xml
View File

@ -300,9 +300,9 @@ local_ip = 9.181.89.203</programlisting>
<step>
<para>Start the Networking L2 agent</para>
<para>The Networking Open vSwitch L2 agent can
be a service of operating system. The
be a service of the operating system. The
command to start depends on your operating
systems. The following command runs the
system. The following command runs the
service directly:</para>
<screen><prompt>#</prompt> <userinput>neutron-openvswitch-agent --config-file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini \
--config-file /etc/neutron/neutron.conf</userinput></screen>
@ -385,7 +385,7 @@ use_namespaces=True</programlisting>
<step>
<para>Start the L3 agent</para>
<para>The Networking L3 agent can be a service
of operating system. The command to start
of the operating system. The command to start
the service depends on your operating
system. The following command starts the
agent directly:</para>
@ -481,11 +481,11 @@ export OS_AUTH_URL=http://<replaceable>controller</replaceable>:5000/v2.0/</prog
this network through provider network.
<literal>router:external true</literal>
means that an external network is created
where you can create floating IP and router
where you can create the floating IP and router
gateway port.</emphasis></para>
</step>
<step>
<para>Add an IP on external network to br-ex.</para>
<para>Add an IP on the external network to br-ex.</para>
<para>Because br-ex is the external network bridge,
add an IP 30.0.0.100/24 to br-ex and ping the
floating IP of the VM from our network
@ -680,7 +680,7 @@ rtt min/avg/max/mdev = 1.234/1.495/1.745/0.211 ms
</computeroutput></screen>
</step>
<step>
<para>Ping floating IP of the TenantA's server:</para>
<para>Ping the floating IP of TenantA's server:</para>
<screen><prompt>$</prompt> <userinput>ping 30.0.0.2</userinput>
<computeroutput>PING 30.0.0.2 (30.0.0.2) 56(84) bytes of data.
64 bytes from 30.0.0.2: icmp_req=1 ttl=63 time=45.0 ms
@ -758,7 +758,7 @@ rtt min/avg/max/mdev = 0.898/15.621/45.027/20.793 ms
provider:segmentation_id) 2 and 3. And
also note the network IDs and subnet IDs
because you use them to create VMs and
router.</para>
the router.</para>
</step>
<step>
<para>Create a server TenantC-VM1 for TenantC