Koteswara Rao Kelam
The patch set contains the code for the L2 gateway scheduler that determines which L2 gateway agent is the Monitor agent out of available agents if there does not exist Monitor agent in the list of active agents. If only one L2 gateway agent is active, then this piece of code makes that agent the Monitor agent. If multiple agents are active, then the logic makes the L2 gateway agent that has the oldest 'started_at' timestamp as the Monitor agent. It makes use of fanout cast message to send it to all the agents. The message payload includes the host name of the Monitor agent so that that particular agent changes its role to the Monitor, whereas other agents who receive this message change their role to default transact agent. The patch set also removes the term TRANSACT as one state "MONITOR" is enough to decide the role. Co-Authored-By: Maruti Kamat <email@example.com> Change-Id: Ib06dbe320021de3653d26f267994ced52480254a
|8 years ago|
|doc/source||8 years ago|
|etc||8 years ago|
|networking_l2gw||8 years ago|
|specs/kilo||8 years ago|
|.coveragerc||8 years ago|
|.gitignore||8 years ago|
|.gitreview||8 years ago|
|.testr.conf||8 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||8 years ago|
|setup.cfg||8 years ago|
|setup.py||8 years ago|
|test-requirements.txt||8 years ago|
|tox.ini||8 years ago|
API's and implementations to support L2 Gateways in Neutron.
- Free software: Apache license
- Source: http://git.openstack.org/cgit/stackforge/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.
The 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.