Since l2gateway binds vxlan(virtual side) to vlan(physical side) segment. We are extracting only vxlan segment from the virtual network. Since multi segment network can have multiple segmentation id's belonging to different network types(vlan, gre, vxlan, etc), we are extracting the vxlan segment from it. We are checking for multiple vxlan segments in the network since ovsdb does not allow multiple vxlan segmentation id's to associate for same vlan (physical side) while creating l2_gateway_connection. For Ex: say multi segment network has two vxlan segment id's 1000 and 2000. If we create a l2_gateway_connection for this network by providing physical side vlan segment as 500, the bindings should be 1000:500 and 2000:500, this is not allowed in ovsdb hardware vtep schema. Closes-Bug:1511639 Change-Id: I5f704eaf40763686aa30320dff7a99a16b6c1772
|7 years ago|
|contrib||8 years ago|
|debian||8 years ago|
|devstack||7 years ago|
|doc/source||8 years ago|
|etc||8 years ago|
|networking_l2gw||7 years ago|
|specs/kilo||8 years ago|
|tools||7 years ago|
|.coveragerc||8 years ago|
|.gitignore||9 years ago|
|.gitreview||8 years ago|
|.testr.conf||7 years ago|
|CONTRIBUTING.rst||9 years ago|
|HACKING.rst||9 years ago|
|LICENSE||9 years ago|
|MANIFEST.in||9 years ago|
|README.rst||8 years ago|
|babel.cfg||9 years ago|
|openstack-common.conf||9 years ago|
|requirements.txt||7 years ago|
|setup.cfg||7 years ago|
|setup.py||8 years ago|
|test-requirements.txt||7 years ago|
|tox.ini||7 years ago|
API's and implementations to support L2 Gateways in Neutron.
- Free software: Apache license
- Source: http://git.openstack.org/cgit/openstack/networking-l2gw
This project proposes a Neutron API extension that can be used to express and manage L2 Gateway components. In the simplest terms L2 Gateways are meant to bridge two or more networks together to make them look at a single L2 broadcast domain.
There are a number of use cases that can be addressed by an L2 Gateway API. Most notably in cloud computing environments, a typical use case is bridging the virtual with the physical. Translate this to Neutron and the OpenStack world, and this means relying on L2 Gateway capabilities to extend Neutron logical (overlay) networks into physical (provider) networks that are outside the OpenStack realm. These networks can be, for instance, VLAN's that may or may not be managed by OpenStack.
For help using or hacking on L2GW, you can send an email to the OpenStack Development Mailing List <mailto:email@example.com>; please use the [L2-Gateway] Tag in the subject. Most folks involved hang out on the IRC channel #openstack-neutron.