Jump to: navigation, search

Tracking ML2 Subgroup Reviews

Revision as of 19:08, 3 July 2014 by Abhraut (talk | contribs) (The guideline for updating this wiki is at the end of this page)


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

Specs Under Review

For categories, please see the description at the bottom.

Title Spec/BP Type Priority Owner Status R1 R2 R3 R4 C1 C2 C3
ML2 Type drivers refactor to allow extensiblity spec Common 2 (Med) asomya Review Sukhdev
+1
yamamoto shivharis banix rkukura - -
GW API: L2 bridging API - Piece 1: Basic use cases spec Common 3 (Low) racha-ben-ali Review - - - - - - -
Neutron QoS API Extension spec Common 3 (Low) sc68cal Review irenab - - - - - -
physical-network-topology extension spec spec Common 3 (Low) yamahata Review Sukhdev yamamoto asomya banix - - -
VLAN aware VMs spec Common 3 (Low) Erik Moe Review - - - - - - -
Support for extensions in ML2 Mechanism Drivers spec BP Common 3 (Low) nlahouti Addressed the review comments and also documented details in[1] and waiting for reply from rkukura banix shivharis matrohon yamamato rkukura
-1
mestery

nlahouti: removed -2. Please refer to status column
-
Neutron External Ports spec BP Common 2 (Med) kevinbenton Review - - - - - - -
API Extension for l2-gateway spec Common 3 (Low) yamahata Review - - - - - - -
ML2 OVS mechanism driver support portsecurity extension spec OVS 3 (Low) yamahata Review - - - - - - -
VDP support in OVS Neutron Agent spec OVS 3 (Low) nlahouti Got 4+ approvals. Provided the clarifications for Akihiro Motoki. Waiting for BP [2] approval. yamamoto
+1
Sukhdev
+1
- - mestery
+2
- -
Open vSwitch-based Security Groups: OVS FirewallDriver spec OVS 3 (Low) asadoughi Review - - - - - - -
Add spec for ML2 mechanism driver for SDN-VE spec Driver 3 (Low) banix Review yamamoto irenab shivharis - - - -
ML2 mechanism driver for Cisco UCS Manager spec BP Driver 3 (Low) sadasu Review Sukhdev
+1
irenab - - rkukura SumitN -
ofagent l2pop support spec Driver 3 (Low) yamamoto Review - - - - - - -
OFAgent: Merge br-int and br-tun spec Driver 3 (Low) yamamoto Review - - - - - - -
Linuxbridge QoS Support spec Driver 3 (Low) oda-g Review - - - - - - -
Provider Segment Support for Cisco Nexus Switches spec Driver 3 (Low) rcurran Review - - - - - - -
ML2 Cisco Nexus Mechanism Driver VxLAN Gateway Support spec Driver 3 (Low) rcurran Review slogan
+1
Sukhdev
-1
- - - - -
ML2 mechanism driver for Huawei SDN controller spec Driver 3 (Low) yangxurong Review Sukhdev - - - - - -
Arista L3 Router Service Plugin spec not 3 (Low) sukhdev Review banix
+1
- - - mastery
+2
- -
Add spec for ML2 mechanism driver for Cisco N1KV spec Driver 3 (Low) abhraut Review
Addressed Edgars comments
emagana - - - - - -
Layer 3 Service Plugin for Cisco Nexus Switches spec not 3 (Low) rcurran Review Sukhdev
-1
- - - - - -
Add spec for ML2 mechanism driver for Snabb NFV spec Driver 3 (Low) lukego Review - - - - - - -

Merged Specs with Code Under Review

Title Spec/BP Owner Code R1 R2 R3 R4 C1 C2 C3 Code Status
Allow partial specification of Provider Network attributes spec zzelle code - - - - - - - -
ML2 Mechanism Driver for Cisco DFA spec nlahouti - - - - - - - - -
ML2 Mechanism Driver for the Cisco APIC spec HenryG - - - - - - - - -
ML2 Mechanism Driver for SR-IOV NIC switching spec irenab - - - - - - - - -
Neutron OVS based Distributed Virtual Router spec swami - - - - - - - - -
L3 router Service plugin for the Cisco APIC spec asomya - - - - - - - - -
Freescale SDN Mechanism Driver spec trinaths code yamamoto - - - mestery amotoki - Merged
ofagent: port monitoring w/o ovsdb accesses spec yamamoto - - - - - - - - -

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

  • The owner of a given spec is responsible for keeping the corresponding row in 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
  • Priority
    • Use the following strings for priority: "1 (High)", "2 (Med)", "3 (Low)" so we can easily sort the table based on the priority if need be
    • If not sure, insert the spec with priority set to 3 (Low)
    • 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
  • Types
    • Common: ML2 common features : features which affects ML2 plugin core or are required by multiple drivers
    • OVS: Open vSwitch mechanism driver / agent : features specific to OVS mech driver or OVS agent. Some blueprints are proposed only for OVS but they are sometimes common to ML2 plugin. I prepared a separate category for OVS (amotoki).
    • Driver: ML2 mechanism driver specific : features specific to a driver

Other Considerations

  • Should we do the same for regular (not specs) neutron reviews? Will that be too much? We can wait and see if the current table will be used and if it will make the review process any better and then decide.
  • Any changes we can make to Launchpad and/or Gerrit review that will make the tracking of the specs easier and that will make using a table like this unnecessary?