Description of problem:
Layer 2 gateway services allow a tenant’s virtual network to be bridged to a physical network. This integration provides users with the capability to access resources on a physical server via a layer 2 network connection rather than via a routed layer 3 connection, i.e extending the L2 broadcast domain instead of going through L3/Floating IP.
To implement this, there is a need to bridge between the virtual workloads running inside an overlay (VXLAN) and workloads running in physical networks (normally using VLAN).
The idea behind hardware VTEPs is to create an overlay network that connects VMs and physical servers and make them think that they’re in the same L2 network even if they’re on opposite sides of the globe. OpenDaylight will manipulate specific OVSDB databases on the VTEP. The database that the controller manipulates will vary depending on the VTEP’s type: if the VTEP is a hypervisor, the controller will expect to manipulate an Open_vSwitch database. If the VTEP is a hardware VTEP, it will expect to manipulate a hardware_vtep database. In both cases, the controller will manipulate the DB using the OVSDB protocol.
Neutron has an L2 GW API: http://docs.openstack.org/developer/networking-l2gw/usage.html
*** Bug 1411420 has been marked as a duplicate of this bug. ***
We think that we can provide the best experience to our customers by offering a certification process for HW VTEP on specific switch models. We won’t fully support the feature until such a certification process exists.
HW VTEP with OpenDaylight will be offered as technology preview for RHOSP 12.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
I have provided doc input and review. All done with doc requirements as far at I can tell. Please let me know if that is not the case.