API's and implementations to support L2 Gateways in Neutron.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
elajkat 73a0f9d198 Remove .zuul.yaml 12 months ago
contrib networking-l2gw debian packaging and installation 6 years ago
debian networking-l2gw debian packaging and installation 6 years ago
devstack Adding l2gw section to tempest.conf within devstack plugin 4 years ago
doc/source Merge "Adding Release and version management for L2GW package" 6 years ago
etc Introduce socket timeout for a blocking socket 5 years ago
networking_l2gw Take allowed-address-pairs to ucast_mac_remote 4 years ago
specs New API SPEC for Border Gateway support 5 years ago
tools Merge "Fix sphinx-docs job for stable branch" into stable/pike 2 years ago
.coveragerc Remove ovsapp references form .coverage file 6 years ago
.gitignore Initial cookiecutter setup 7 years ago
.gitreview OpenDev Migration Patch 2 years ago
.testr.conf Add API tests for L2Gateway extension 6 years ago
CONTRIBUTING.rst Update the documentation link for doc migration 4 years ago
HACKING.rst Update the documentation link for doc migration 4 years ago
LICENSE Initial cookiecutter setup 7 years ago
MANIFEST.in Include alembic migrations in module 5 years ago
README.rst Update the documentation link for doc migration 4 years ago
babel.cfg Initial cookiecutter setup 7 years ago
bindep.txt Retire networking-l2gw: remove zuul jobs 1 year ago
openstack-common.conf Initial cookiecutter setup 7 years ago
requirements.txt Updated from global requirements 4 years ago
setup.cfg Update the documentation link for doc migration 4 years ago
setup.py Use neutron-lib's context module 4 years ago
test-requirements.txt Updated from global requirements 4 years ago
tox.ini Fix unit tests for Pike 3 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