x
/
networking-l2gw
Code Issues Proposed changes
API's and implementations to support L2 Gateways in Neutron.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
208 Commits
11 Branches
21 Tags
1.1 MiB
Python 97.9%
Shell 2%
Mako 0.1%
 
 
 
master
stable/zed
stable/victoria
stable/wallaby
stable/pike
stable/queens
stable/rocky
stable/stein
stable/train
stable/ussuri
stable/ocata
19.0.0
18.0.0
17.0.1
17.0.0
16.0.0
15.0.0
14.0.0
13.0.0
12.0.1
12.0.0.0rc1
12.0.0
newton-eol
11.0.0
mitaka-eol
10.1.0.a1
10.0.0
liberty-eol
kilo-eol
2016.1.0
1.0.0
2015.1.1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'a381726b53'
${ noResults }
Go to file
vikas a381726b53 support multi segment network for l2gw connection 
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 networking-l2gw debian packaging and installation 8 years ago
debian networking-l2gw debian packaging and installation 8 years ago
devstack Fix for HP 3rd Party CI failure 7 years ago
doc/source Merge "Adding Release and version management for L2GW package" 8 years ago
etc Service driver support in L2gw for south bound 8 years ago
networking_l2gw support multi segment network for l2gw connection 7 years ago
specs/kilo Fix typos in networking-l2gw repo 8 years ago
tools Networking-L2Gateway CI fails 7 years ago
.coveragerc Change ignore-errors to ignore_errors 8 years ago
.gitignore Initial cookiecutter setup 9 years ago
.gitreview Update .gitreview file for project rename 8 years ago
.testr.conf Revert "Fix for HP 3rd Party CI failure" 7 years ago
CONTRIBUTING.rst Initial cookiecutter setup 9 years ago
HACKING.rst Initial cookiecutter setup 9 years ago
LICENSE Initial cookiecutter setup 9 years ago
MANIFEST.in Initial cookiecutter setup 9 years ago
README.rst Follow up on namespace renaming 8 years ago
babel.cfg Initial cookiecutter setup 9 years ago
openstack-common.conf Initial cookiecutter setup 9 years ago
requirements.txt Updated from global requirements 7 years ago
setup.cfg Update translation setup 7 years ago
setup.py Updated from global requirements 8 years ago
test-requirements.txt Updated from global requirements 7 years ago
tox.ini Networking-L2Gateway CI fails 7 years ago

README.rst

networking-l2gw

API's and implementations to support L2 Gateways in Neutron.

L2 Gateways

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.

Initial implementation

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.

More information

For help using or hacking on L2GW, you can send an email to the OpenStack Development Mailing List <mailto:openstack-dev@lists.openstack.org>; please use the [L2-Gateway] Tag in the subject. Most folks involved hang out on the IRC channel #openstack-neutron.

Getting started

  • TODO