openstack/openstack-manuals
Code Issues Proposed changes

Fix spelling of Linux Bridge, Open vSwitch, Hyper-V

Browse Source 
Get this consistent across all manuals.

Change-Id: Id5f99aae69ef39eeb6b98ffe93a9f7f8f349d42e
This commit is contained in:
Andreas Jaeger 2013-10-05 13:48:10 +02:00
parent 585b9be742
commit 58d8100ed3
7 changed files with 28 additions and 28 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/admin-guide-cloud/ch_networking.xml
View File

@ -384,20 +384,20 @@
on each hypervisor to perform local vswitch
configuration. The agent that runs depends on
the plug-in that you use, and some plug-ins do
not require an agent. </para>
not require an agent.</para>
</listitem>
<listitem>
<para><emphasis role="bold">dhcp agent</emphasis>
(<literal>neutron-dhcp-agent</literal>).
Provides DHCP services to tenant networks.
Some plug-ins use this agent. </para>
Some plug-ins use this agent.</para>
</listitem>
<listitem>
<para><emphasis role="bold">l3 agent</emphasis>
<literal>(neutron-l3-agent</literal>).
Provides L3/NAT forwarding to provide external
network access for VMs on tenant networks.
Some plug-ins use this agent. </para>
Some plug-ins use this agent.</para>
</listitem>
</itemizedlist>
<para>These agents interact with the main neutron process
@ -915,7 +915,7 @@
</listitem>
<listitem>
<para><literal>compute</literal> is
created by Compute. </para>
created by Compute.</para>
</listitem>
</itemizedlist>
</note>
@ -1423,7 +1423,7 @@
<td>True</td>
</tr>
<tr>
<td>LinuxBridge</td>
<td>Linux Bridge</td>
<td>True</td>
<td>True</td>
</tr>

18
doc/admin-guide-cloud/section_networking_adv_features.xml
View File

@ -62,7 +62,7 @@
network</emphasis>. A virtual network that
a tenant or an administrator creates. The
physical details of the network are not
exposed to the tenant. </para>
exposed to the tenant.</para>
</listitem>
<listitem>
<para><emphasis role="bold">provider
@ -1094,7 +1094,7 @@
firewall rule can be associated with only
one firewall policy at a time. However,
the association can be changed to a
different firewall policy. </td>
different firewall policy.</td>
</tr>
<tr>
<td>shared</td>
@ -1133,7 +1133,7 @@
<td>source_port</td>
<td>Integer or String (either as a single port
number or in the format of a ':' separated
range) </td>
range)</td>
<td>None</td>
<td>Source port number or a range.</td>
</tr>
@ -1141,7 +1141,7 @@
<td>destination_port</td>
<td>Integer or String (either as a single port
number or in the format of a ':' separated
range) </td>
range)</td>
<td>None</td>
<td>Destination port number or a range.</td>
</tr>
@ -1234,7 +1234,7 @@
<td>This is an ordered list of firewall rule
uuids. The firewall applies the rules in
the order in which they appear in this
list. </td>
list.</td>
</tr>
<tr>
<td>audited</td>
@ -1248,7 +1248,7 @@
or the associated firewall rules are
changed, this attribute is set to False
and must be explicitly set to True through
an update operation. </td>
an update operation.</td>
</tr>
</tbody>
</table>
@ -1306,7 +1306,7 @@
<tr>
<td>status</td>
<td>String</td>
<td>N/A </td>
<td>N/A</td>
<td><para>Indicates whether the firewall is
currently operational. Possible values
include:</para>
@ -1353,7 +1353,7 @@
<screen><prompt>$</prompt> <userinput>neutron firewall-rule-create --protocol &lt;tcp|udp|icmp|any&gt; --destination-port &lt;port-range&gt; --action &lt;allow|deny&gt;</userinput></screen>
<para>The CLI requires that a protocol value be
provided. If the rule is protocol agnostic,
the 'any' value can be used. </para>
the 'any' value can be used.</para>
<para>In addition to the protocol attribute, other
attributes can be specified in the firewall
rule. See the previous section for the
@ -1411,7 +1411,7 @@
<note>
<para>The allowed-address-pairs extension is currently
only supported by the following plug-ins: ML2, Nicira
NVP, and OpenvSwitch.</para>
NVP, and Open vSwitch.</para>
</note>
<section xml:id="section_allowed_address_pairs_workflow">
<title>Basic allowed address pairs operations</title>

4
doc/config-reference/networking/section_networking-plugins.xml
View File

@ -14,7 +14,7 @@
implement the logical API requests. Some OpenStack Networking plugins might use
basic Linux VLANs and IP tables, while others might use more advanced
technologies, such as L2-in-L3 tunneling or OpenFlow. The following sections
detail the configuration options for the various plugins available. </para>
detail the configuration options for the various plugins available.</para>
<section xml:id="networking-plugin-bigswitch">
<title>BigSwitch configuration options</title>
<xi:include href="../../common/tables/neutron-bigswitch.xml"/>
@ -32,7 +32,7 @@
<xi:include href="../../common/tables/neutron-hyperv.xml"/>
</section>
<section xml:id="networking-plugin-linuxbridge">
<title>Linux bridge configuration options</title>
<title>Linux Bridge configuration options</title>
<xi:include href="../../common/tables/neutron-linuxbridge.xml"/>
</section>
<section xml:id="networking-plugin-mlnx">

8
doc/config-reference/networking/section_networking-scenarios.xml
View File

@ -372,10 +372,10 @@ bridge_mappings = physnet1:br-ex,physnet2:br-eth1</programlisting>
</section>
</section>
<section xml:id="under_the_hood_linuxbridge">
<title>Linux bridge</title>
<para>This section describes how the Linux bridge plug-in implements the OpenStack
<title>Linux Bridge</title>
<para>This section describes how the Linux Bridge plug-in implements the OpenStack
Networking abstractions. For information about DHCP and L3 agents, see <xref
linkend="under_the_hood_openvswitch_scenario1"/>. </para>
linkend="under_the_hood_openvswitch_scenario1"/>.</para>
<section xml:id="under_the_hood_linuxbridge_configuration">
<title>Configuration</title>
<para>This example uses VLAN isolation on the switches to isolate tenant networks. This configuration labels the physical
@ -481,7 +481,7 @@ physical_interface_mappings = physnet2:eth1</programlisting></para>
<imagedata fileref="../../common/figures/under-the-hood-scenario-1-linuxbridge-network.png" contentwidth="6in"/>
</imageobject>
</mediaobject>
<para>The following figure shows how the Linux bridge plug-in uses network namespaces to
<para>The following figure shows how the Linux Bridge plug-in uses network namespaces to
provide isolation.</para><note><para>veth pairs form connections between the
Linux bridges and the network namespaces.</para></note><mediaobject>
<imageobject>

2
doc/glossary/glossary-terms.xml
View File

@ -2624,7 +2624,7 @@ daemon that provides
</glossdef>
</glossentry>
<glossentry>
<glossterm>Linux bridge neutron plug-in</glossterm>
<glossterm>Linux Bridge neutron plug-in</glossterm>
<glossdef>
<para>Plugin that allows a Linux bridge to understand
a neutron port, interface attachment, and other

2
doc/install-guide/ch_installnetworking.xml
View File

@ -720,7 +720,7 @@ interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver</programlist
<screen><computeroutput>interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver</computeroutput></screen>
</listitem>
<listitem>
<para>A plugin that uses LinuxBridge, you must
<para>A plugin that uses Linux Bridge, you must
set:</para>
<screen><computeroutput>interface_driver = neutron.agent.linux.interface.BridgeInterfaceDriver</computeroutput></screen>
</listitem>

12
doc/training-guide/module002-ch001-networking-in-openstack.xml
View File

@ -32,7 +32,7 @@
as the NIC of a virtual server, to a virtual network.
Also describes the associated network configuration,
such as the MAC and IP addresses to be used on that
port. </para>
port.</para>
</listitem>
</itemizedlist>
<para>You can configure rich network topologies by creating
@ -193,7 +193,7 @@
</itemizedlist>
<para>OpenStack Networking relies on the OpenStack Identity
Project (Keystone) for authentication and authorization of all
API request. </para>
API request.</para>
<para>OpenStack Compute interacts with OpenStack Networking
through calls to its standard API. As part of creating a VM,
nova-compute communicates with the OpenStack Networking API to
@ -239,20 +239,20 @@
network:</emphasis>Used for internal communication
between OpenStack Components. The IP addresses on this
network should be reachable only within the data
center. </para>
center.</para>
</listitem>
<listitem>
<para><emphasis role="bold">Data network:</emphasis>Used
for VM data communication within the cloud deployment.
The IP addressing requirements of this network depend
on the OpenStack Networking plugin in use. </para>
on the OpenStack Networking plugin in use.</para>
</listitem>
<listitem>
<para><emphasis role="bold">External
network:</emphasis>Used to provide VMs with Internet
access in some deployment scenarios. The IP addresses
on this network should be reachable by anyone on the
Internet. </para>
Internet.</para>
</listitem>
<listitem>
<para><emphasis role="bold">API network:</emphasis>Exposes
@ -266,4 +266,4 @@
block.</para>
</listitem>
</itemizedlist>
</chapter>
</chapter>