openstack/openstack-manuals
Code Issues Proposed changes

cleanup section_neutron-provider-router-with-private_networks

Browse Source 
added to before the public network
occur doesn't need to be plural
added open parenthesis, it was missing

Change-Id: I96b93cca962cfbce93741c25c29ee71e5ca5e09d
This commit is contained in:
Shilla Saebi 2014-02-18 19:21:07 -05:00
parent 8d94af1f02
commit 9ca173f559
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/install-guide/section_neutron-provider-router-with-private_networks.xml
View File

@ -49,7 +49,7 @@
<td><para>Compute</para></td>
<td><para>Runs Compute and the Networking L2
agent.</para>
<para>This node does not have access the public
<para>This node does not have access to the public
network.</para>
<para>The node must have a network interface that
communicates with the controller node through
@ -306,7 +306,7 @@ admin_password = <replaceable>NEUTRON_PASS</replaceable></programlisting>
</step>
<step>
<para>All VM communication between the nodes
occurs through the <literal>br-eth1</literal>
occur through the <literal>br-eth1</literal>
bridge.</para>
<para>Create the <literal>br-eth1</literal>
network bridge:</para>
@ -647,7 +647,7 @@ export OS_AUTH_URL="http://<replaceable>controller</replaceable>:5000/v2.0/"</pr
traffic.</para>
<para>The router provides L3 connectivity among private
networks. Tenants can reach instances for other tenants
unless you use additional filtering, such as, security
(unless you use additional filtering, such as, security
groups). With a single router, tenant networks cannot use
overlapping IPs. To resolve this issue, the administrator
can create private networks on behalf of the