Jump to: navigation, search

Difference between revisions of "Neutron/L2-GW"

(Use Cases)
Line 31: Line 31:
  
 
== Use Cases  ==
 
== Use Cases  ==
 +
 +
To be filled in.
 +
Feel free to add your use case here.

Revision as of 18:35, 31 January 2015

Overview

L2-GW (Layer-2 Gateway) is a service plugin within OpenStack Networking (Neutron) service. L2-GW is being developed outside the main Neutron tree as a separate stack-forge project. L2-GW service plugin operates in conjunction with ML2 plugin/drivers and leverages l2pop driver.

For the past few cycles several stake holders have been discussing L2 Gateway to mean different things. Mostly, their definition has dependent upon their use case. In a general sense, L2 gateway is an entity or resource which bridges two L2 domains (or networks) to achieve one seamless L2 broadcast domain. In this case, it is assumed that at least one of L2 domains is Neutron orchestrated and the other L2 domain could be neutron or non-neutron (legacy) domain. Depending upon the characteristics of a L2 domain (e.g. VLANs, overlay tunnel, another open-stack domain, etc), may cause folks to think different definition or implementations of L2 gateway.

In order to make forward progress, and define an initial version of the L2 GW API, the team decided to take one use case and move forward. There is explicit understanding that this API may not cover all use cases, even though it will be desired to cover as many use cases as possible. Use cases section is added to this wiki to list known use cases which pertain to L2 Gateway.

Meetings

L2-GW team meets bi-weekly. The meeting details can be found at IRC meetings

Blueprints and Specs

Kilo Release Specs

Team's charter is to implement initial version of L2-GW API in Kilo cycle. The spec is available here:

Code Reviews

To see active patches under review, please see here:

To see the merged patches, please see here:

Project Repo

L2-Gateway project is implemented as a stack forge project. Please see the project repo here:

Use Cases

To be filled in. Feel free to add your use case here.