There is no good reason why these must be explicitly set in local.conf by the poor guy or gal. We can be nice and have them be automatically set by the devstack plugin. Change-Id: Idf39758147e8f3ea8fe9beb4f580fff391bf8380 Related-bug: #1541244
|7 years ago|
|contrib||8 years ago|
|debian||8 years ago|
|devstack||7 years ago|
|doc/source||8 years ago|
|etc||7 years ago|
|networking_l2gw||7 years ago|
|specs/kilo||7 years ago|
|tools||7 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||8 years ago|
|README.rst||8 years ago|
|babel.cfg||8 years ago|
|openstack-common.conf||8 years ago|
|requirements.txt||7 years ago|
|setup.cfg||7 years ago|
|setup.py||7 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:firstname.lastname@example.org>; please use the [L2-Gateway] Tag in the subject. Most folks involved hang out on the IRC channel #openstack-neutron.