Difference between revisions of "Tracking ML2 Subgroup Reviews"
(→Specs proposed to Kilo Release) |
(→Merged Specs along with Merged Code in Juno) |
||
| Line 19: | Line 19: | ||
|- | |- | ||
| [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] || | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|} | |} | ||
Revision as of 00:29, 4 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 |
|---|---|---|---|
| portsecurity extension support | Isaku Yamahata | port-sec-extWIP | |
| ML2 hierarchical port binding | rkukura | api db logic |
Planned
| Title | Spec/BP | Owner | Comment |
|---|---|---|---|
| Modular L2 Agent | banix | On hold | |
| ofagent: sub driver | BP | 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
- 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?
