Jump to: navigation, search

Difference between revisions of "Tracking ML2 Subgroup Reviews"

(Merged Specs along with Merged Code in Juno)
(Specs proposed to Kilo Release)
 
(6 intermediate revisions by 3 users not shown)
Line 15: Line 15:
 
!! scope="col"| Code
 
!! scope="col"| Code
 
!!  scope="col" | Status  
 
!!  scope="col" | Status  
 +
!!  scope="col" | Comments
 
|-  
 
|-  
| [https://review.openstack.org/#/c/99873/ portsecurity extension support] || Isaku Yamahata || [https://review.openstack.org/126552 port-sec-ext][https://review.openstack.org/150835 WIP] ||
+
| [https://review.openstack.org/#/c/99873/ portsecurity extension support] || Isaku Yamahata || [https://review.openstack.org/#/c/129178/ passing db entry extend dict] [https://review.openstack.org/#/c/152759/ passing plugin context to ext driver] [https://review.openstack.org/#/c/152759/ extension_driver][https://review.openstack.org/126552 port-sec-ext][https://review.openstack.org/150835 WIP] || ||  
 
|-  
 
|-  
| [https://review.openstack.org/#/c/106185/  ML2 hierarchical port binding]  ||rkukura ||  [https://review.openstack.org/#/c/115110/ api] [https://review.openstack.org/#/c/116122/ db] [https://review.openstack.org/#/c/116209/ logic] ||  
+
| [https://review.openstack.org/#/c/106185/  ML2 hierarchical port binding]  ||rkukura ||  [https://review.openstack.org/#/c/115110/ api] [https://review.openstack.org/#/c/116122/ db] [https://review.openstack.org/#/c/116209/ logic] || merged || need additional tests
 
|}
 
|}
  
Line 25: Line 26:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Title !! Spec/BP !! Owner !! Comment  
+
! Title/BP !! Owner !! Comment  
 +
|-
 +
| ML2 Async driver invocation || manishg || [https://review.openstack.org/#/c/154333 poc-code]
 
|-  
 
|-  
| Modular L2 Agent ||   || banix  || On hold
+
| Modular L2 Agent || banix  || On hold
 
|-  
 
|-  
| ofagent: sub driver || [https://blueprints.launchpad.net/neutron/+spec/ofagent-sub-driver BP] ||  yamamoto  || probably some overlap with modular l2 agent  
+
| [https://blueprints.launchpad.net/neutron/+spec/ofagent-sub-driver ofagent: sub driver] ||  yamamoto  || probably some overlap with modular l2 agent  
 
|}
 
|}
  
Line 36: Line 39:
 
* Mechanism Drivers do not need a blueprint starting Kilo Release (?)
 
* Mechanism Drivers do not need a blueprint starting Kilo Release (?)
 
* The owner of a given spec is responsible for keeping the corresponding row in this table up to date
 
* 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 ([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
 
* 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 ===
 
=== 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.
 
* 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?
 
* 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?

Latest revision as of 13:41, 18 February 2015


Here are tables for tracking the status of the specs related to ML2 in current release.

The guideline for updating this wiki is at the end of this page

Specs proposed to Kilo Release

For categories, please see the description at the bottom.

Title Owner Code Status Comments
portsecurity extension support Isaku Yamahata passing db entry extend dict passing plugin context to ext driver extension_driverport-sec-extWIP
ML2 hierarchical port binding rkukura api db logic merged need additional tests

Planned

Title/BP Owner Comment
ML2 Async driver invocation manishg poc-code
Modular L2 Agent banix On hold
ofagent: sub driver yamamoto probably some overlap with modular l2 agent

Guide

  • Mechanism Drivers do not need a blueprint starting Kilo Release (?)
  • The owner of a given spec is responsible for keeping the corresponding row in this table up to date


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?