Jump to: navigation, search

Tracking ML2 Subgroup Reviews

Revision as of 21:12, 16 December 2014 by Shh (talk | contribs) (Specs deferred to Kilo Release)


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

Merged Specs along with Merged Code in Juno

Title Spec/BP Owner Priority Code R1 R2 R3 R4 C1 C2 C3 Code Status
ML2 Type drivers refactor to allow extensiblity spec asomya 2 (Med) abandoned code1 code2 code3 - - - - - - - code1 & code2 merged
ML2 Mechanism Driver for Cisco DFA spec nlahouti 3 (Low) code1 code2 code3 code4 banix yamamoto rossella_s - - - - code1 merged
ofagent: port monitoring w/o ovsdb accesses spec yamamoto 3 (Low) 108915 (devstack) - - - - - - - Merged
ofagent l2pop support spec yamamoto 3 (Low) all merged - - - - - - - Merged
OFAgent: Merge br-int and br-tun spec yamamoto 3 (Low) all merged - - - - - - - Merged
ofagent: physical interface mappings spec yamamoto 3 (Low) all merged - - - - - - - Merged
Support for extensions in ML2 spec nlahouti 3 (Low) code - - - - - - - Merged
Arista L3 Router Service Plugin spec sukhdev 3 (Low) code - - - - - - - Merged
Layer 3 Service Plugin for Brocade VDX Switches spec shivharis 3 (Low) code - - - - - - - Merged
Allow partial specification of Provider Network attributes spec zzelle 3 (Low) code1 code2 code3 - - - - - - - Merged
ML2 Mechanism Driver for the Cisco APIC spec HenryG 3 (Low) code1 Code2 - - - - - - - Merged
ML2 Mechanism Driver for SR-IOV NIC switching spec irenab 3 (Low) code1 code2 - - - - - - - Merged
Neutron OVS based Distributed Virtual Router spec swami 1 (High) (DVR subteam) - - - - - - - ML2 related review is merged
Freescale SDN Mechanism Driver spec trinaths 3 (Low) code yamamoto - - - mestery amotoki - Merged

Specs proposed to Kilo Release

For categories, please see the description at the bottom.

Title Spec/BP Type Priority Code Owner Status R1 R2 R3 R4 C1 C2 C3
portsecurity extension support
DPDKOVS - ML2 DPDK OVS Support
neutron port traffic rate support for SR-IOV NIC
Kilo ML2 type driver refactoring
ML2 Mechanism Driver for Mellanox SDN

Specs deferred to Kilo Release

For categories, please see the description at the bottom.

Title Spec/BP Type Priority Code Owner Status R1 R2 R3 R4 C1 C2 C3
GW API: L2 bridging API - Piece 1: Basic use cases spec Common 3 (Low) racha-ben-ali deferred - - - - - - -
Neutron QoS API Extension spec Common 3 (Low) sc68cal deferred irenab - - - - - -
physical-network-topology extension spec spec Common 3 (Low) yamahata deferred Sukhdev yamamoto asomya banix - - -
VLAN aware VMs spec Common 3 (Low) Erik Moe deferred - - - - - - -
API Extension for l2-gateway spec Common 3 (Low) yamahata deferred - - - - - - -
ML2 OVS mechanism driver support portsecurity extension spec OVS 3 (Low) yamahata deferred - - - - - - -
Open vSwitch-based Security Groups: OVS FirewallDriver spec OVS 3 (Low) asadoughi deferred - - - - - - -
Linuxbridge QoS Support spec Driver 3 (Low) oda-g deferred - - - - - - -
Provider Segment Support for Cisco Nexus Switches spec Driver 3 (Low) rcurran deferred gessau
+1
pcm
+1
- - - - -
ML2 Cisco Nexus Mechanism Driver VxLAN Gateway Support spec Driver 3 (Low) rcurran deferred gessau
+1
pcm
+1
asomya
+1
- - - -
Layer 3 Service Plugin for Cisco Nexus Switches spec not 3 (Low) rcurran deferred Sukhdev
+1
pcm
+1
gessau
+1
asomya
+1
- - -
ML2 hierarchical port binding spec 1 (High) api db logic rkukura deferred - - - - - - -
Neutron External Ports spec 2 (Med) code code2 kevinbenton deferred - - - - - - -
VDP Support in OVS Neutron Agent spec 3 (Low) code1 code2 code3 padkrish deferred Yamamoto - - - amotoki - -
ML2 mechanism driver for Huawei SDN controller spec 3 (Low) code yangxurong deferred - - - - - - -
ML2 mechanism driver for Cisco UCS Manager spec 3 (Low) code sadasu deferred - - - - - - -
Add spec for ML2 mechanism driver for SDN-VE spec 3 (Low) N/A mprabhu deferred Yamamoto
+1
banix
+1
- - Mark - -
Add spec for ML2 mechanism driver for Snabb NFV spec 3 (Low) code lukego deerred - - - - - - -
Add spec for ML2 mechanism driver for Cisco N1KV spec 3 (Low) N/A abhraut deferred - - - - - - -
DPDKOVS - ML2 DPDK OVS Support spec Driver 3 (Low) N/A sean-k-mooney new - - - - - - -

Planned

Title Spec/BP Owner Comment
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?