openstack
/
networking-l2gw
Code Issues Proposed changes
RETIRED, API's and implementations to support L2 Gateways in Neutron.
261 Commits
7 Branches
1 Tag
7 MiB
Go to file
vikas af5c24232e delete stale ovsdb table entries from mysql db 
whenever l2gateway_agnet.ini is reconfigured to the same ovsdb identifier
but different IP, then we need to clean the mysql db entries from earlier
configured ovsdb_identifier and IP.

For Ex: l2gateway_agent is connected to "ovsdb1:10.10.10.10:6632",
but when you change l2gateway_agent.ini to "ovsdb1:20.20.20.20:6632",
then the mysql entries related to "ovsdb1:10.10.10.10:6632" should be cleaned.

Change-Id: I72cd5a5e2ea27c2a6b37865c3517e614f901aecf
Closes-Bug:1588809
 		2016-06-09 03:51:33 -07:00
contrib networking-l2gw debian packaging and installation 2015-04-07 03:06:22 -07:00
debian networking-l2gw debian packaging and installation 2015-03-26 03:23:55 -07:00
devstack Fix L2GW service framework for out-of-tree drivers. 2016-03-31 15:12:52 +05:30
doc/source Merge "Adding Release and version management for L2GW package" 2015-04-29 22:55:24 +00:00
etc configurable port option for l2gw agent 2016-05-26 23:38:24 -07:00
networking_l2gw delete stale ovsdb table entries from mysql db 2016-06-09 03:51:33 -07:00
specs/kilo l2-gateway-api.rst: Make it clear where VNI is taken from 2016-03-23 17:11:21 +09:00
tools Networking-L2Gateway CI fails 2016-02-11 02:51:10 -08:00
.coveragerc Remove ovsapp references form .coverage file 2016-02-19 00:10:35 -08:00
.gitignore Initial cookiecutter setup 2014-12-11 23:42:16 -08:00
.gitreview Update .gitreview file for project rename 2015-06-12 23:12:30 +00:00
.testr.conf Revert "Fix for HP 3rd Party CI failure" 2016-01-11 12:01:57 -08:00
CONTRIBUTING.rst Initial cookiecutter setup 2014-12-11 23:42:16 -08:00
HACKING.rst Initial cookiecutter setup 2014-12-11 23:42:16 -08:00
LICENSE Initial cookiecutter setup 2014-12-11 23:42:16 -08:00
MANIFEST.in Initial cookiecutter setup 2014-12-11 23:42:16 -08:00
README.rst Follow up on namespace renaming 2015-06-29 14:02:44 -07:00
babel.cfg Initial cookiecutter setup 2014-12-11 23:42:16 -08:00
openstack-common.conf Initial cookiecutter setup 2014-12-11 23:42:16 -08:00
requirements.txt Updated from global requirements 2016-06-02 04:05:19 +00:00
setup.cfg Update translation setup 2016-01-29 07:12:09 +09:00
setup.py Updated from global requirements 2015-09-18 16:38:56 +00:00
test-requirements.txt Updated from global requirements 2016-02-08 02:40:05 +00:00
tox.ini Networking-L2Gateway CI fails 2016-02-11 02:51:10 -08:00

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