Depends-On: I131ee0d720b1a3c1b0091e1a8d303774138063da Depends-On: I668ca20ef8a0371324173506427849603ebcdcc3 Change-Id: Id43067b3304a4e819708a2d00440e033d09bdc66 Signed-off-by: Ricardo Noriega <firstname.lastname@example.org>
|6 years ago|
|contrib||8 years ago|
|debian||8 years ago|
|devstack||6 years ago|
|doc/source||8 years ago|
|etc||6 years ago|
|networking_l2gw||6 years ago|
|specs||6 years ago|
|tools||6 years ago|
|.coveragerc||7 years ago|
|.gitignore||8 years ago|
|.gitreview||8 years ago|
|.testr.conf||7 years ago|
|CONTRIBUTING.rst||8 years ago|
|HACKING.rst||8 years ago|
|LICENSE||8 years ago|
|MANIFEST.in||6 years ago|
|README.rst||8 years ago|
|babel.cfg||8 years ago|
|openstack-common.conf||8 years ago|
|requirements.txt||6 years ago|
|setup.cfg||6 years ago|
|setup.py||6 years ago|
|test-requirements.txt||6 years ago|
|tox.ini||6 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.