Difference between revisions of "Tracking ML2 Subgroup Reviews"
(→Under Review) |
m |
||
Line 1: | Line 1: | ||
Here are tables for tracking the status of the specs related to ML2 in Juno: --[[User:Banix|Banix]] ([[User talk:Banix|talk]]) 01:37, 10 June 2014 (UTC) | Here are tables for tracking the status of the specs related to ML2 in Juno: --[[User:Banix|Banix]] ([[User talk:Banix|talk]]) 01:37, 10 June 2014 (UTC) | ||
− | + | The guideline for updating this wiki is at the [[#section Guide|end of this page]]. | |
− | |||
− | |||
=== Under Review === | === Under Review === | ||
Line 90: | Line 88: | ||
| ofagent: sub driver || [https://blueprints.launchpad.net/neutron/+spec/ofagent-sub-driver BP] || yamamoto || probably some overlap with modular l2 agent | | ofagent: sub driver || [https://blueprints.launchpad.net/neutron/+spec/ofagent-sub-driver BP] || yamamoto || probably some overlap with modular l2 agent | ||
|} | |} | ||
+ | |||
+ | === Guide === | ||
+ | |||
+ | * For an spec, the owner is responsible for keeping this table up to date | ||
+ | * A reviewer can add her name to the table when she reviews a spec but ultimately the spec owner needs to make sure the information is up to date | ||
+ | * The priority of specs were decided to be defined as follows ([http://eavesdrop.openstack.org/meetings/networking_ml2/2014/networking_ml2.2014-06-11-16.03.log.html IRC Log]): | ||
+ | ** So mestery suggests vendor-specific drivers should be at low priority, consistent with vendor plugins and vendor service drivers | ||
+ | ** The ML2 team can identify 2 or 3 BPs to treat as high priority | ||
+ | ** These need to be of general community interest, and really important to complete for Juno | ||
+ | ** And we can identify several more BPs to treat as medium priority, which also should be of general community interest |
Revision as of 03:09, 13 June 2014
Here are tables for tracking the status of the specs related to ML2 in Juno: --Banix (talk) 01:37, 10 June 2014 (UTC)
The guideline for updating this wiki is at the end of this page.
Contents
Under Review
Title | Spec/BP | Owner | Status | R1 | R2 | R3 | R4 | c1 | c2 | c3 |
---|---|---|---|---|---|---|---|---|---|---|
Add spec for ML2 mechanism driver for SDN-VE | spec | banix | WIP | - | - | - | - | - | - | - |
VDP support in OVS Neutron Agent | spec | nlahouti | Review | yamamoto +1 | - | - | - | - | - | - |
ML2 Type drivers refactor to allow extensiblity | spec | asomya | Review | Sukhdev | yamamoto | shivharis | banix | rkukura | - | - |
physical-network-topology extension spec | spec | yamahata | Review | Sukhdev | yamamoto | asomya | banix | - | - | - |
GW API: L2 bridging API - Piece 1: Basic use cases | spec | racha-ben-ali | Review | - | - | - | - | - | - | - |
Neutron QoS API Extension | spec | sc68cal | Review | irenab | - | - | - | - | - | - |
Allow partial specification of Provider Network attributes | spec | zzelle | Review | Sukhdev | - | - | - | rkukura | - | - |
Open vSwitch-based Security Groups: OVS FirewallDriver | spec | asadoughi | Review | - | - | - | - | - | - | - |
Support for extensions in ML2 Mechanism Drivers | spec BP | nlahouti | Review | banix | shivharis | mrohon | yamamato | rkukura | - | - |
Neutron External Ports | spec BP | kevinbenton | Review | - | - | - | - | - | - | - |
VLAN aware VMs | spec | Erik Moe | Review | - | - | - | - | - | - | - |
ML2 mechanism driver for Cisco UCS Manager | spec BP | sadasu | Review | Sukhdev | irenab | - | - | rkukura | SumitNaiksatam | - |
ofagent l2pop support | spec | yamamoto | Blocked | - | - | - | - | - | - | - |
ofagent: port monitoring w/o ovsdb accesses | spec | yamamoto | Review | banix | - | - | - | - | - | - |
Arista L3 Router Service Plugin | spec | sukhdev | Review | banix | - | - | - | mestery | - | - |
Linuxbridge QoS Support | spec | oda-g | Review | - | - | - | - | - | - | - |
Provider Segment Support for Cisco Nexus Switches | spec | rcurran | Review | - | - | - | - | - | - | - |
Layer 3 Service Plugin for Cisco Nexus Switches | spec | rcurran | Review | - | - | - | - | - | - | - |
ML2 Cisco Nexus Mechanism Driver VxLAN Gateway Support | spec | rcurran | Review | - | - | - | - | - | - | - |
Merged
Title | Spec/BP | Owner | Status |
---|---|---|---|
ML2 Mechanism Driver for Cisco DFA | spec | nlahouti | Merged |
ML2 Mechanism Driver for the Cisco APIC | spec | HenryG | Merged |
ML2 Mechanism Driver for SR-IOV NIC switching | spec | irenab | Merged |
Neutron OVS based Distributed Virtual Router | spec | swami | Merged |
L3 router Service plugin for the Cisco APIC | spec | asomya | Merged |
Freescale SDN Mechanism Driver | spec | trinaths | Merged |
Planned
Title | Spec/BP | Owner | Comment |
---|---|---|---|
ML2 Hierarchical Port Binding | rkukura | Under development | |
Modular L2 Agent | banix | Under development | |
ofagent: sub driver | BP | yamamoto | probably some overlap with modular l2 agent |
Guide
- For an spec, the owner is responsible for keeping this table up to date
- A reviewer can add her name to the table when she reviews a spec but ultimately the spec owner needs to make sure the information is up to date
- The priority of specs were decided to be defined as follows (IRC Log):
- So mestery suggests vendor-specific drivers should be at low priority, consistent with vendor plugins and vendor service drivers
- The ML2 team can identify 2 or 3 BPs to treat as high priority
- These need to be of general community interest, and really important to complete for Juno
- And we can identify several more BPs to treat as medium priority, which also should be of general community interest