Adds comparison of Tenant and Provider networks

Adds an in-depth description of each of the available network types
and discusses options for tenant and provider networks.

Change-Id: I02c92669e141d80a4f86a4ec6e8bd54ce9567c67
Closes-Bug: 1298775
This commit is contained in:
Martin Lopes 2014-03-28 16:07:10 +10:00
parent fff915174d
commit 460b9fc271
3 changed files with 21407 additions and 0 deletions

View File

@ -182,5 +182,85 @@
</tbody> </tbody>
</table> </table>
</para> </para>
</section>
<section xml:id="tenant-provider-networks">
<title>Tenant and provider networks</title>
<para>
The following diagram presents an overview of the tenant and provider
network types, and illustrates how they interact within the overall
Networking topology:
</para>
<para>
<figure>
<title>Tenant and provider networks</title>
<mediaobject>
<imageobject>
<imagedata scale="90"
fileref="../../common/figures/NetworkTypes.png"/>
</imageobject>
</mediaobject>
</figure>
</para>
<formalpara>
<title>Tenant networks</title>
<para>Tenant networks are created by users for connectivity within projects;
they are fully isolated by default and are not shared with other projects.
Networking supports a range of tenant network types:
</para>
</formalpara>
<para>
<variablelist>
<varlistentry>
<term>Flat</term>
<listitem>
<para>All instances reside on the same network, which can
also be shared with the hosts. No VLAN tagging or other
network segregation takes place.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>Local</term>
<listitem>
<para>Instances reside on the local compute host and are
effectively isolated from any external networks.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>VLAN</term>
<listitem>
<para>Networking allows users to create multiple provider
or tenant networks using VLAN IDs (802.1Q tagged) that
correspond to VLANs present in the physical network. This
allows instances to communicate with each other across
the environment. They can also communicate with dedicated
servers, firewalls, load balancers and other networking
infrastructure on the same layer 2 VLAN.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>VXLAN and GRE</term>
<listitem>
<para>VXLAN and GRE use network overlays to support private
communication between instances. A Networking router is
required to enable traffic to traverse outside of the GRE or
VXLAN tenant network. A router is also required to connect
directly-connected tenant networks with external networks,
including the Internet; the router provides the ability to
connect to instances directly from an external network using
floating IP addresses.</para>
</listitem>
</varlistentry>
</variablelist>
</para>
<formalpara>
<title>Provider networks</title>
<para>Provider networks are created by the OpenStack administrator and map
directly to an existing physical network in the data center. Useful
network types in this category are flat (untagged) and VLAN (802.1Q
tagged). It is possible to allow provider networks to be shared among
tenants as part of the network creation process.</para>
</formalpara>
</section> </section>
</section> </section>

Binary file not shown.

After

Width:  |  Height:  |  Size: 74 KiB

File diff suppressed because it is too large Load Diff

After

Width:  |  Height:  |  Size: 638 KiB