openstack/openstack-manuals
Code Issues Proposed changes

A note on partial specs support in ML2 for gre/vxlan provider networks

Browse Source 
ML2 plug-in allows admins to choose some provider network attributes
 and let neutron choose remaining attributes. This change provides
 the implementation for GRE/VXLAN provider networks.

Change-Id: I9281aa5eff6389345a216c64e9b739eb7b334114
Closes-Bug: #1346695
This commit is contained in:
Alexander Adamov 2015-02-04 14:53:46 +02:00
parent ca291a44f2
commit e8a946457c
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/admin-guide-cloud/networking/section_networking-scenarios.xml
View File

@ -690,7 +690,14 @@ physical_interface_mappings = physnet2:eth1</programlisting>
plug-in can be extended through mechanism drivers, allowing multiple mechanisms to be
used simultaneously. This section describes different <emphasis>ML2</emphasis> plug-in
and agent configurations with different type drivers and mechanism drivers.</para>
<para>Previously, Networking deployments were only able to use the plug-in that had been
<note>
<para>Currently, there is no need to define <parameter>SEGMENTATION_ID</parameter>
network provider attribute for GRE and VXLAN network types. The choice can be
delegated to Networking, in such case ML2 plug-in tries to find a network
in tenant network pools which respects specified provider network attributes.
</para>
</note>
<para>Previously, Networking deployments were only able to use the plug-in that had been
selected at implementation time. For example, a deployment running the Open vSwitch
plug-in was only able to use Open vSwitch exclusively; it wasn't possible to
simultaneously run another plug-in such as Linux Bridge. This was found to be a