Difference between revisions of "Tracking ML2 Subgroup Reviews"
m (→Under Review) |
|||
| Line 3: | Line 3: | ||
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 [[#Guide|end of this page]] | + | == The guideline for updating this wiki is at the [[#Guide|end of this page]] == |
| − | === Under Review === | + | |
| + | |||
| + | === Specs Under Review === | ||
For categories, please see the description at the bottom. | For categories, please see the description at the bottom. | ||
| Line 36: | Line 38: | ||
| Support for extensions in ML2 Mechanism Drivers || [https://review.openstack.org/#/c/89208/ spec] [https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mechanismdriver-extensions BP] || Common || 3 (Low) || nlahouti || Review || banix || shivharis || mrohon || yamamato || rkukura <br /> -1 || mestery <br /> -2 || - | | Support for extensions in ML2 Mechanism Drivers || [https://review.openstack.org/#/c/89208/ spec] [https://blueprints.launchpad.net/neutron/+spec/neutron-ml2-mechanismdriver-extensions BP] || Common || 3 (Low) || nlahouti || Review || banix || shivharis || mrohon || yamamato || rkukura <br /> -1 || mestery <br /> -2 || - | ||
|- | |- | ||
| − | | Neutron External Ports || [https://review.openstack.org/#/c/87825/ spec] [https://blueprints.launchpad.net/neutron/+spec/neutron-external-ports BP] || Common || | + | | Neutron External Ports || [https://review.openstack.org/#/c/87825/ spec] [https://blueprints.launchpad.net/neutron/+spec/neutron-external-ports BP] || Common || 3 (Low) || kevinbenton || Review || - || - || - || - || - || - || - |
|- | |- | ||
| API Extension for l2-gateway || [https://review.openstack.org/#/c/100278/ spec] || Common || 3 (Low) || yamahata || Review || - || - || - || - || - || - || - | | API Extension for l2-gateway || [https://review.openstack.org/#/c/100278/ spec] || Common || 3 (Low) || yamahata || Review || - || - || - || - || - || - || - | ||
| Line 46: | Line 48: | ||
| Open vSwitch-based Security Groups: OVS FirewallDriver || [https://review.openstack.org/#/c/89712/ spec] || OVS|| 3 (Low) || asadoughi || Review || - || - || - || - || - || - || - | | Open vSwitch-based Security Groups: OVS FirewallDriver || [https://review.openstack.org/#/c/89712/ spec] || OVS|| 3 (Low) || asadoughi || Review || - || - || - || - || - || - || - | ||
|- | |- | ||
| − | | Add spec for ML2 mechanism driver for SDN-VE || [https://review.openstack.org/#/c/88101/ spec] || | + | | Add spec for ML2 mechanism driver for SDN-VE || [https://review.openstack.org/#/c/88101/ spec] || Driver || 3 (Low) || banix || Review || yamamoto <br /> +1 || irenab || - || - || - || - || - |
|- | |- | ||
| − | | ML2 mechanism driver for Cisco UCS Manager || [https://review.openstack.org/#/c/95236/ spec] [https://blueprints.launchpad.net/neutron/+spec/ml2-ucs-manager-mechanism-driver BP] || | + | | ML2 mechanism driver for Cisco UCS Manager || [https://review.openstack.org/#/c/95236/ spec] [https://blueprints.launchpad.net/neutron/+spec/ml2-ucs-manager-mechanism-driver BP] || Driver || 3 (Low) || sadasu || Review || Sukhdev <br /> -1 || irenab || - || - || rkukura || SumitN || - |
|- | |- | ||
| − | | ofagent l2pop support || [https://review.openstack.org/#/c/89463/ spec] || | + | | ofagent l2pop support || [https://review.openstack.org/#/c/89463/ spec] || Driver || 3 (Low) || yamamoto || Review || - || - || - || - || - || - || - |
|- | |- | ||
| − | | ofagent: port monitoring w/o ovsdb accesses || [https://review.openstack.org/#/c/91742/ spec] || | + | | ofagent: port monitoring w/o ovsdb accesses || [https://review.openstack.org/#/c/91742/ spec] || Driver || 3 (Low) || yamamoto || Review || banix <br /> +1 || - || - || - || Nachi <br /> +2 || - || - |
|- | |- | ||
| − | | Linuxbridge QoS Support || [https://review.openstack.org/#/c/96331/ spec] || | + | | Linuxbridge QoS Support || [https://review.openstack.org/#/c/96331/ spec] || Driver || 3 (Low) || oda-g || Review || - || - || - || - || - || - || - |
|- | |- | ||
| − | | Provider Segment Support for Cisco Nexus Switches || [https://review.openstack.org/#/c/95834 spec] || | + | | Provider Segment Support for Cisco Nexus Switches || [https://review.openstack.org/#/c/95834 spec] || Driver || 3 (Low) || rcurran ||Review || - || - || - || - || - || - || - |
|- | |- | ||
| − | | ML2 Cisco Nexus Mechanism Driver VxLAN Gateway Support || [https://review.openstack.org/#/c/98177/ spec] || | + | | ML2 Cisco Nexus Mechanism Driver VxLAN Gateway Support || [https://review.openstack.org/#/c/98177/ spec] || Driver || 3 (Low) || rcurran || Review || slogan <br /> +1 || Sukhdev <br /> -1 || - || - || - || - || - |
|- | |- | ||
| − | | ML2 mechanism driver for Huawei SDN controller || [https://review.openstack.org/#/c/97490/ spec] || | + | | ML2 mechanism driver for Huawei SDN controller || [https://review.openstack.org/#/c/97490/ spec] || Driver || 3 (Low) || yangxurong || Review || - || - || - || - || - || - || - |
|- | |- | ||
| − | | Arista L3 Router Service Plugin || [https://review.openstack.org/#/c/97125/ spec] || not || 3 (Low) | + | | Arista L3 Router Service Plugin || [https://review.openstack.org/#/c/97125/ spec] || not || 3 (Low) || sukhdev || Review || banix <br /> +1 || - || - || - || mastery <br /> +2 || - || - |
|- | |- | ||
| Layer 3 Service Plugin for Cisco Nexus Switches || [https://review.openstack.org/#/c/95910/ spec] || not || 3 (Low) || rcurran || Review || Sukhdev <br /> -1 || - || - || - || - || - || - | | Layer 3 Service Plugin for Cisco Nexus Switches || [https://review.openstack.org/#/c/95910/ spec] || not || 3 (Low) || rcurran || Review || Sukhdev <br /> -1 || - || - || - || - || - || - | ||
|} | |} | ||
| − | === Merged Specs=== | + | === Merged Specs with Code Under Review === |
{| class="wikitable" | {| class="wikitable" | ||
| Line 110: | Line 112: | ||
|} | |} | ||
| − | + | = Guide = | |
* 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 | ||
| Line 122: | Line 124: | ||
*** These need to be of general community interest, and really important to complete for Juno | *** 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 | *** And we can identify several more BPs to treat as medium priority, which also should be of general community interest | ||
| − | * | + | * Types |
| − | ** ML2 common features : features which affects ML2 plugin core or are required by multiple drivers | + | ** Common: ML2 common features : features which affects ML2 plugin core or are required by multiple drivers |
| − | ** 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). | + | ** 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). |
| − | ** ML2 mechanism driver specific : features specific to a driver | + | ** 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? | ||
Revision as of 02:59, 19 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
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 | Review | banix | shivharis | mrohon | yamamato | rkukura -1 |
mestery -2 |
- |
| Neutron External Ports | spec BP | Common | 3 (Low) | 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 | Review | yamamoto +1 |
Sukhdev +1 |
- | - | - | - | - |
| 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 +1 |
irenab | - | - | - | - | - |
| 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: port monitoring w/o ovsdb accesses | spec | Driver | 3 (Low) | yamamoto | Review | banix +1 |
- | - | - | Nachi +2 |
- | - |
| 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 | - | - | - | - | - | - | - |
| Arista L3 Router Service Plugin | spec | not | 3 (Low) | sukhdev | Review | banix +1 |
- | - | - | mastery +2 |
- | - |
| Layer 3 Service Plugin for Cisco Nexus Switches | spec | not | 3 (Low) | rcurran | Review | Sukhdev -1 |
- | - | - | - | - | - |
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 | - | - | - | - | - | - | - | - | - |
| 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 |
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?
