OpenStack - User contributions [en]

Meetings/GroupBasedPolicy

2016-06-02T14:43:12Z

Hemanthravi: /* June 2nd, May 26th, 2016 */

Weekly meeting page for the Group Based Policy (GBP) team occurring Thursdays at 1800 UTC on #openstack-meeting-3

Announcements for this week:

==Wiki ==
The group wiki page can be accessed at https://wiki.openstack.org/wiki/GroupBasedPolicy

== Mailing List ==
Please use [Group-based-policy] in the subject line of your emails to the OpenStack Development Mailing List <openstack-dev@lists.openstack.org> when possible.

== Meetings ==

=== Standing items ===

* Bugs:
** [https://bugs.launchpad.net/group-based-policy/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=CRITICAL&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search Critical], [https://bugs.launchpad.net/group-based-policy/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=HIGH&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search High], [https://bugs.launchpad.net/group-based-policy/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=MEDIUM&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&search=Search Medium]

* Functional/Integration Tests

* Packaging Update

* Docs

=== June 2nd, May 26th, 2016 ===

* [https://review.openstack.org/#/c/301701/ QoS Support]
* [https://review.openstack.org/#/q/topic:bp/gbp-network-services-framework NFP Implementation patches]
**[https://review.openstack.org/#/c/309145/83/devstack/README-NFP Devstack README]
**[https://wiki.openstack.org/wiki/GroupBasedPolicy/GerritQueries/NFP#NFP_Implementation_Patches Patches desc]

=== May 19th, 2016 ===

* [https://review.openstack.org/#/q/topic:bp/gbp-network-services-framework NFP Implementation patches]
* Intra-PTG communication

=== May 12th, 2016 ===

* [https://review.openstack.org/#/q/topic:bp/gbp-network-services-framework NFP Implementation patches]

=== April 21st, 2016 ===
* Amit Bose +2/A privileges for APIC driver patches
* [https://review.openstack.org/239743 Network Function Plugin Framework for GBP]
* [https://review.openstack.org/#/c/306855 Devrefs]

=== April 7th, 2016 ===
* [https://review.openstack.org/239743 Network Function Plugin Framework for GBP]
* [https://review.openstack.org/#/c/300557 GBP Devstack Plugin]

=== March 24th, 17th, 10th, 2016 ===
* Addition of status attributes
** https://review.openstack.org/289127
** https://review.openstack.org/289530
* Other Design Specs
* Austin summit workshop

=== March 3rd, 2016 ===
* Design Specs
** [https://review.openstack.org/239743 Network Function Plugin Framework for GBP]
*** [https://review.openstack.org/#/c/282292 Multi process framework]
** [https://review.openstack.org/#/c/275358/ Initial support for Quality of Service]

=== Feb 26th, 18th, 11th, 4th, 2016 ===
* [https://review.openstack.org/#/q/topic:mitaka-sync Mitaka Sync patches]
* Design Specs
** [https://review.openstack.org/239743 Network Function Plugin Framework for GBP]
*** [https://review.openstack.org/#/c/282292 Multi process framework]
** [https://review.openstack.org/#/c/275358/ Initial support for Quality of Service]

=== Jan 28th, 2016 ===
* Addition of status attribute to resources
* Cross-project clean-up patches:
** [https://review.openstack.org/264642 use of assertions]
** [https://review.openstack.org/263188 log.warn]

=== Jan 21st, 2016 ===
* Liberty stable branch

=== Jan 7th, 2016 ===
* [https://review.openstack.org/#/q/topic:liberty-sync Liberty sync patches]

== Meeting Logs ==
* [http://eavesdrop.openstack.org/meetings/networking_policy/2016/?C=M;O=D 2016]
* [http://eavesdrop.openstack.org/meetings/networking_policy/2015/?C=M;O=D 2015]
* [http://eavesdrop.openstack.org/meetings/networking_policy/2014/?C=M;O=D 2014]
* [http://eavesdrop.openstack.org/meetings/networking_policy/2013/?C=M;O=D 2013]
* [http://eavesdrop.openstack.org/meetings/networking_policy/ Older logs]

== Archives ==
* [https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy/MeetingMinutesArchive Meeting Agenda]

GroupBasedPolicy/GerritQueries/NFP

2016-06-02T14:33:59Z

Hemanthravi: /* NFP Implementation Patches */

=== NFP Implementation Patches ===

[https://review.openstack.org/#/q/topic:bp/gbp-network-services-framework Patch Stack]
# [https://review.openstack.org/#/c/282292 Multi process framework implementation]Implements python multiprocessing based distributor and worker processes to handle the RPC messages. This framework implements the processing model for the NFP functionality. The framework implements an event and queue mechanism for the communication between the distributor and worker processes, along with primitives to serialize processing of events. The implementation includes a polling mechanism to handle periodic tasks. The NFP functionality is organized as modules, with each module registering for RPCs and events the module handles. The framework loads the modules and invokes the init method of the modules.
# [https://review.openstack.org/#/c/298206 DB Framework and DB Model Implementation]Implements the DB model and access methods for the NFP resources. The NFP DB model includes resources for network functions, network function instances, network function devices and the associated gbp resources.
# [https://review.openstack.org/#/c/298213 Openstack client library for NFP]Implements a common abstraction to interface with neutron and gbp APIs. Implements utility methods to interface with openstack clients for nova, neutron, gbp and keystone.
# [https://review.openstack.org/#/c/298224 Service Orchestrator module]
# [https://review.openstack.org/#/c/298288 Added Base mode support in Service Orchestrator]
# [https://review.openstack.org/#/c/298297 Adding Device Orchestrator]
# [https://review.openstack.org/#/c/298312 Orchestration drivers with their unit tests]
# [https://review.openstack.org/#/c/298374 Heat driver implementation]
# [https://review.openstack.org/#/c/298380 Node Driver]

GroupBasedPolicy/GerritQueries/NFP

2016-06-02T14:32:09Z

Hemanthravi: /* NFP Implementation Patches */

=== NFP Implementation Patches ===

[https://review.openstack.org/#/q/topic:bp/gbp-network-services-framework Patch Stack]
# [https://review.openstack.org/#/c/282292 Multi process framework implementation]Implements python multiprocessing based distributor and worker processes to handle the RPC messages. This framework implements the processing model for the NFP functionality. The framework implements an event and queue mechanism for the communication between the distributor and worker processes, along with primitives to serialize processing of events. The implementation includes a polling mechanism to handle periodic tasks. The NFP functionality is organized as modules, with each module registering for RPCs and events the module handles. The framework loads the modules and invokes the init method of the modules.
# [https://review.openstack.org/#/c/298206 DB Framework and DB Model Implementation]
Implements the DB model and access methods for the NFP resources. The NFP DB model includes resources for network functions, network function instances, network function devices and the associated gbp resources.
# [https://review.openstack.org/#/c/298213 Openstack client library for NFP]
Implements a common abstraction to interface with neutron and gbp APIs. Implements utility methods to interface with openstack client methods for nova, neutron, gbp and keystone.
# [https://review.openstack.org/#/c/298224 Service Orchestrator module]
# [https://review.openstack.org/#/c/298288 Added Base mode support in Service Orchestrator]
# [https://review.openstack.org/#/c/298297 Adding Device Orchestrator]
# [https://review.openstack.org/#/c/298312 Orchestration drivers with their unit tests]
# [https://review.openstack.org/#/c/298374 Heat driver implementation]
# [https://review.openstack.org/#/c/298380 Node Driver]

GroupBasedPolicy/GerritQueries/NFP

2016-06-02T14:31:30Z

Hemanthravi: /* NFP Implementation Patches */

=== NFP Implementation Patches ===

[https://review.openstack.org/#/q/topic:bp/gbp-network-services-framework Patch Stack]
# [https://review.openstack.org/#/c/282292 Multi process framework implementation]
Implements python multiprocessing based distributor and worker processes to handle the RPC messages. This framework implements the processing model for the NFP functionality. The framework implements an event and queue mechanism for the communication between the distributor and worker processes, along with primitives to serialize processing of events. The implementation includes a polling mechanism to handle periodic tasks. The NFP functionality is organized as modules, with each module registering for RPCs and events the module handles. The framework loads the modules and invokes the init method of the modules.
# [https://review.openstack.org/#/c/298206 DB Framework and DB Model Implementation]
Implements the DB model and access methods for the NFP resources. The NFP DB model includes resources for network functions, network function instances, network function devices and the associated gbp resources.
# [https://review.openstack.org/#/c/298213 Openstack client library for NFP]
Implements a common abstraction to interface with neutron and gbp APIs. Implements utility methods to interface with openstack client methods for nova, neutron, gbp and keystone.
# [https://review.openstack.org/#/c/298224 Service Orchestrator module]
# [https://review.openstack.org/#/c/298288 Added Base mode support in Service Orchestrator]
# [https://review.openstack.org/#/c/298297 Adding Device Orchestrator]
# [https://review.openstack.org/#/c/298312 Orchestration drivers with their unit tests]
# [https://review.openstack.org/#/c/298374 Heat driver implementation]
# [https://review.openstack.org/#/c/298380 Node Driver]

GroupBasedPolicy/GerritQueries/NFP

2016-06-01T22:42:40Z

Hemanthravi: /* NFP Implementation Patches */

=== NFP Implementation Patches ===

[https://review.openstack.org/#/q/topic:bp/gbp-network-services-framework Patch Stack]
# [https://review.openstack.org/#/c/282292 Multi process framework implementation]
Implements python multiprocessing based distributor and worker processes to handle the RPC messages. This framework implements the processing model for the NFP functionality. The framework implements an event and queue mechanism for the communication between the distributor and worker processes, along with primitives to serialize processing of events. The implementation includes a polling mechanism to handle periodic tasks. The NFP functionality is organized as modules, with each module registering for RPCs and events the module handles. The framework loads the modules and invokes the init method of the modules.
# [https://review.openstack.org/#/c/298206 DB Framework and DB Model Implementation]
Implements the DB model and access methods for the NFP resources. The NFP DB model includes resources for network functions, network function instances, network function devices and the associated gbp resources.
# [https://review.openstack.org/#/c/298213 Openstack client library for NFP]
Implements a common abstraction to interface with neutron and gbp APIs. Implements utility methods to interface with openstack client methods for nova, neutron, gbp and keystone.
# [https://review.openstack.org/#/c/298224 Service Orchestrator module]
# [https://review.openstack.org/#/c/298288 Added Base mode support in Service Orchestrator]
# [https://review.openstack.org/#/c/298297 Adding Device Orchestrator]
# [https://review.openstack.org/#/c/298312 Orchestration drivers with their unit tests]
# [https://review.openstack.org/#/c/298374 Heat driver implementation]
# [https://review.openstack.org/#/c/298380 Node Driver]

GroupBasedPolicy/GerritQueries/NFP

2016-06-01T01:18:48Z

Hemanthravi: /* NFP Implementation Patches */

=== NFP Implementation Patches ===

[https://review.openstack.org/#/q/topic:bp/gbp-network-services-framework Patch Stack]
# [https://review.openstack.org/#/c/282292 Multi process framework implementation]
Implements python multiprocessing based distributor and worker processes to handle the RPC messages. This framework implements the processing model for the NFP functionality. The framework implements an event and queue mechanism for the communication between the distributor and worker processes, along with primitives to serialize processing of events. The implementation includes a polling mechanism to handle periodic tasks. The NFP functionality is organized as modules, with each module registering for RPCs and events the module handles. The framework loads the modules and invokes the init method of the modules.
# [https://review.openstack.org/#/c/298206 DB Framework and DB Model Implementation]
Implements the DB model and access methods for the NFP resources. The NFP DB model includes resources for network functions, network function instances, network function devices and the associated gbp resources.
# [https://review.openstack.org/#/c/298213 Openstack client library for NFP]
# [https://review.openstack.org/#/c/298224 Service Orchestrator module]
# [https://review.openstack.org/#/c/298288 Added Base mode support in Service Orchestrator]
# [https://review.openstack.org/#/c/298297 Adding Device Orchestrator]
# [https://review.openstack.org/#/c/298312 Orchestration drivers with their unit tests]
# [https://review.openstack.org/#/c/298374 Heat driver implementation]
# [https://review.openstack.org/#/c/298380 Node Driver]

GroupBasedPolicy/GerritQueries/NFP

2016-05-12T23:36:49Z

Hemanthravi: /* NFP Implementation Patches */

=== NFP Implementation Patches ===

[https://review.openstack.org/#/q/topic:bp/gbp-network-services-framework Patch Stack]
# [https://review.openstack.org/#/c/282292 Multi process framework implementation]
# [https://review.openstack.org/#/c/298206 DB Framework and DB Model Implementation]
# [https://review.openstack.org/#/c/298213 Openstack client library for NFP]
# [https://review.openstack.org/#/c/298224 Service Orchestrator module]
# [https://review.openstack.org/#/c/298288 Added Base mode support in Service Orchestrator]
# [https://review.openstack.org/#/c/298297 Adding Device Orchestrator]
# [https://review.openstack.org/#/c/298312 Orchestration drivers with their unit tests]
# [https://review.openstack.org/#/c/298374 Heat driver implementation]
# [https://review.openstack.org/#/c/298380 Node Driver]

GroupBasedPolicy/GerritQueries/NFP

2016-05-12T23:27:30Z

Hemanthravi: /* NFP Implementation Patches */

=== NFP Implementation Patches ===

[https://review.openstack.org/#/q/topic:bp/gbp-network-services-framework Patch Stack]
# [https://review.openstack.org/#/c/282292:Multi process framework implementation]
# [https://review.openstack.org/#/c/298206:DB Framework and DB Model Implementation]
# [https://review.openstack.org/#/c/298213:Openstack client library for NFP]
# [https://review.openstack.org/#/c/298224:Service Orchestrator module]
# [https://review.openstack.org/#/c/298288:Added Base mode support in Service Orchestrator]
# [https://review.openstack.org/#/c/298297:Adding Device Orchestrator]
# [https://review.openstack.org/#/c/298312:Orchestration drivers with their unit tests]
# [https://review.openstack.org/#/c/298374:Heat driver implementation]
# [https://review.openstack.org/#/c/298380:Node Driver]

Neutron Plugins and Drivers

2014-09-15T22:25:41Z

Hemanthravi: /* Existing Plugin and Drivers */

=== Introduction ===
Ensuring release quality through proper testing is an important tenant of the OpenStack community and Neutron team wants to do our part. We are introducing changes below provide more visibility into the quality and stability of vendor plugin and driver code. The policies described here are in effect immediately.

=== Rationale ===
Code proposals for third party plugins have always presented a review challenge for the Neutron core team. In the early days, code was often proposed by core project contributors and our review process only validated whether the requirements were met for community coding style and unit testing. As Neutron has added new resources via extensions, it has become more difficult for Neutron reviewers to ensure the proposed code is functional. Many of the plugins and/or drivers require proprietary hardware and/or software to conduct such testing.

In addition to testing changes, the Neutron team is revising the requirements for the point of contact for third party code. The changes bring the written expectations for contacts in line with current practice.

=== Plugin and Driver Processes ===
Getting a plugin or driver merged upstream into Neutron allows you the benefit of being a part of the simultaneous release, and likely having your plugin or driver packaged with distributions which ship releases based on the simultaneous releases from upstream. However, this is not a "free ride", you should ideally be giving back more than you are taking by getting your code upstream. When you submit your code, you're putting a burden on the existing reviews and infrastructure. The same goes with subsequent bug fixes and backports to stable releases. Thus, you should have someone from your company or team reviewing other code upstream, participating in meetings, etc. The following is a list of requirements for inclusion of code upstream:
* Code which passes review, has adequate unit tests, and passes pep8 guidelines.
* A [http://ci.openstack.org/third_party.html functioning CI system], which has been running successfully against your plugin/driver patches, and other patches as well.
* Participation in Neutron meetings, IRC channels, and email lists.
* A member of the plugin/driver team participating in code reviews of other upstream code.

=== Removal of Upstream Plugins or Drivers ===
If you fail to meet the criteria above, you risk having your plugin or driver removed from upstream. The core team will continue to evaluate third party CI systems to ensure they are running and correctly testing patches for third party plugins and drivers. If they fail to function, an email will be sent to the openstack-dev mailing list asking for the owner to fix this issue. Ideally, the owner will reply to the email thread, and will work with the Neutron and Infra teams to address the CI issue. If no reply is received or if adequate progress is not being made to address the issue within 2 weeks, a process to remove the plugin or driver from upstream will commence. To get your plugin or driver upstream after it has been removed will take a functioning third party CI system running for a month, correctly voting on changes upstream.

=== Point of Contact Requirements ===
Each third party plugin and/or driver shall designate a point of contact for each coordinated release cycle. The contact will serve as a liaison between the Neutron core team and the vendor or community supporting the plugin or driver. The contact shall:

* Attend weekly Neutron team IRC meetings
* Be an active reviewer and contributor
* Be an active participant on openstack-dev mailing list
* Assist the core team with triaging bugs specific to the plugin and/or driver
* Ensure OpenStack development deadlines are properly communicated back to their company and/or community

=== Testing Requirements ===
https://wiki.openstack.org/wiki/NeutronThirdPartyTesting

=== Existing Plugin and Drivers ===
Plugins and drivers currently in the Neutron project repository will be given a grace period until the Icehouse-2 milestone to implement external third party testing. At that time, the Neutron team will release a list of the compatible plugins and drivers (i.e. those that meet the testing requirements). Plugins and drivers that do not have external testing will be deprecated at the Icehouse release and will be candidates for removal when the J-release cycle opens.

The page [[ThirdPartySystems]] gathers information about all third party CI system (including Neutron related).

{| class="wikitable"
|-
! Vendor !! Plugin/Driver Name !! Contact Name !! Status !! Recheck command !! Notes
|-
| Neutron Team || ML2 - OVS/LB || Infra Team || Y || || Covered by Infra (Jenkins)
|-
| A10 Networks || LBaaS Driver || Doug Wiegley || Y || recheck-a10 || None
|-
| Arista Networks || ML2 Driver || Sukhdev Kapur || Y || recheck/reverify no bug/bug # || None
|-
| Big Switch || Plugin || Kevin Benton || Y || recheck-bigswitch || None
|-
| Big Switch || ML2 Driver || Kevin Benton || Y || || None
|-
| Brocade || Vyatta Plugin || Karthik Natarajan || Y || || None
|-
| Brocade || ML2 Driver || Shiv Haris || Y || || None
|-
| Cisco || Plugin - NXOS || Dane Leblanc || N || || It is deprecated and It will be removed in Juno
|-
| Cisco || Plugin - N1Kv || Dane Leblanc || Y || || None
|-
| Cisco || ML2 - APIC || Dane Leblanc || Y || || None
|-
| Cisco || ML2 - DFA || Dane Leblanc || Y || || None
|-
| Cisco || ML2 - NXOS || Dane Leblanc || Y || || None
|-
| Cisco || VPNaaS - Driver || Dane Leblanc || Y || || None
|-
| Cloudbase Solutions || Plugin - Hyper-V || Alessandro Pilotti || Y || check hyper-v || None
|-
| Embrane || Plugin || Ignacio Scopetta || N ||embrane-recheck|| CI fails for their own plugin commits: https://review.openstack.org/#/c/108226/
|-
| Embrane || LBaaS - Driver || Ignacio Scopetta || N ||embrane-recheck|| No CI in place. Candidate to be removed from Neutron
|-
| Freescale || ML2 - Driver || Trinath Somanchi || Y ||recheck freescale|| None
|-
| Freescale || FWaaS - Plugin || Trinath Somanchi || Y ||recheck freescale || None
|-
| IBM || Plugin - SDN-VE || Daya Kamath || Y || || None
|-
| Juniper || Plugin - Contrail || Rudra Rugge || Y || || None
|-
| Mellanox || Plugin || Omri Marcovitch || N || recheck mlnx || It is deprecated. Will be removed in Kilo
|-
| Mellanox || ML2 - Driver || Omri Marcovitch || Y || recheck mlnx || None
|-
| Mellanox || ML2 - Sriovnic switch || Omri Marcovitch || Y || recheck mlnx || None
|-
| Metaplugin || Plugin - Multiple || NTT Team || N || || It is missing some Neutron commits
|-
| Midokura || Plugin - Midonet || Lucas Eznarriaga || Y || recheck midokura|| None
|-
| NEC || Plugin - OpenFlow || Akihiro Motoki || Y || recheck-nec || None
|-
| Citrix NetScaler || LBaaS - Driver || Parikshit Manur || Y || || None
|-
| Nuage Networks || Plugin - VSP || Franck Yelles || Y || || None
|-
| OFAgent || ML2 - OF || Yamamoto Takashi || Y || recheck-ryu || None
|-
| One Convergence || Plugin - NVSD || Hemanth Ravi || Y || recheck oneconvergence|| None
|-
| OpenDaylight || ML2 - ODL || Dave Tucker (dave_tucker) / Kyle Mestery (mestery) || Y || recheck-opendaylight || None
|-
| PLUMgrid || Plugin - Director || Fawad Khaliq || Y || || None
|-
| Ryu || Plugin - Ryu Controller || Yamamoto Takashi || Y || recheck-ryu || It is been deprecated and It will be removed in Kilo
|-
| Radware || LBaaS - Driver || Samuel Bercovici || N || || CI does not exist. Should be removed from Neutron
|-
| Tail-f NCS || ML2 - NCS || Luke Gorrie || Y || || None
|-
| vArmour || FWaaS || Gary Duan || Y || recheck varmour || None
|-
| VMware || Plugin - NSX || Aaron Rosen || Y || || None
|}

Neutron Plugins and Drivers

2014-08-20T04:35:54Z

Hemanthravi:

=== Introduction ===
Ensuring release quality through proper testing is an important tenant of the OpenStack community and Neutron team wants to do our part. We are introducing changes below provide more visibility into the quality and stability of vendor plugin and driver code. The policies described here are in effect immediately.

=== Rationale ===
Code proposals for third party plugins have always presented a review challenge for the Neutron core team. In the early days, code was often proposed by core project contributors and our review process only validated whether the requirements were met for community coding style and unit testing. As Neutron has added new resources via extensions, it has become more difficult for Neutron reviewers to ensure the proposed code is functional. Many of the plugins and/or drivers require proprietary hardware and/or software to conduct such testing.

In addition to testing changes, the Neutron team is revising the requirements for the point of contact for third party code. The changes bring the written expectations for contacts in line with current practice.

=== Plugin and Driver Processes ===
Getting a plugin or driver merged upstream into Neutron allows you the benefit of being a part of the simultaneous release, and likely having your plugin or driver packaged with distributions which ship releases based on the simultaneous releases from upstream. However, this is not a "free ride", you should ideally be giving back more than you are taking by getting your code upstream. When you submit your code, you're putting a burden on the existing reviews and infrastructure. The same goes with subsequent bug fixes and backports to stable releases. Thus, you should have someone from your company or team reviewing other code upstream, participating in meetings, etc. The following is a list of requirements for inclusion of code upstream:
* Code which passes review, has adequate unit tests, and passes pep8 guidelines.
* A [http://ci.openstack.org/third_party.html functioning CI system], which has been running successfully against your plugin/driver patches, and other patches as well.
* Participation in Neutron meetings, IRC channels, and email lists.
* A member of the plugin/driver team participating in code reviews of other upstream code.

=== Removal of Upstream Plugins or Drivers ===
If you fail to meet the criteria above, you risk having your plugin or driver removed from upstream. The core team will continue to evaluate third party CI systems to ensure they are running and correctly testing patches for third party plugins and drivers. If they fail to function, an email will be sent to the openstack-dev mailing list asking for the owner to fix this issue. Ideally, the owner will reply to the email thread, and will work with the Neutron and Infra teams to address the CI issue. If no reply is received or if adequate progress is not being made to address the issue within 2 weeks, a process to remove the plugin or driver from upstream will commence. To get your plugin or driver upstream after it has been removed will take a functioning third party CI system running for a month, correctly voting on changes upstream.

=== Point of Contact Requirements ===
Each third party plugin and/or driver shall designate a point of contact for each coordinated release cycle. The contact will serve as a liaison between the Neutron core team and the vendor or community supporting the plugin or driver. The contact shall:

* Attend weekly Neutron team IRC meetings
* Be an active reviewer and contributor
* Be an active participant on openstack-dev mailing list
* Assist the core team with triaging bugs specific to the plugin and/or driver
* Ensure OpenStack development deadlines are properly communicated back to their company and/or community

=== Testing Requirements ===
https://wiki.openstack.org/wiki/NeutronThirdPartyTesting

=== Existing Plugin and Drivers ===
Plugins and drivers currently in the Neutron project repository will be given a grace period until the Icehouse-2 milestone to implement external third party testing. At that time, the Neutron team will release a list of the compatible plugins and drivers (i.e. those that meet the testing requirements). Plugins and drivers that do not have external testing will be deprecated at the Icehouse release and will be candidates for removal when the J-release cycle opens.

{| class="wikitable"
|-
! Vendor !! Plugin/Driver Name !! Contact Name !! Status !! Notes
|-
| Neutron Team || ML2 - OVS/LB || Infra Team || Y || Covered by Infra (Jenkins)
|-
| A10 Networks || LBaaS Driver || Doug Wiegley || Y || None
|-
| Arista Networks || ML2 Driver || Sukhdev Kapur || Y || None
|-
| Big Switch || Plugin || Kevin Benton || Y || 8.5 hour delay
|-
| Big Switch || ML2 Driver || Kevin Benton || Y || 8.5 hour delay
|-
| Brocade || Vyatta Plugin || Karthik Natarajan || Y || None
|-
| Brocade || ML2 Driver || Shiv Haris || Y || None
|-
| Cisco || Plugin - NXOS || Dane Leblanc || N || It will be removed in Juno
|-
| Cisco || Plugin - N1Kv || Dane Leblanc || Y || None
|-
| Cisco || ML2 - APIC || Dane Leblanc || N || Results are not accurate. Needs clarification from Cisco
|-
| Cisco || ML2 - DFA || Dane Leblanc || N || Needs clarification from Cisco
|-
| Cisco || ML2 - NXOS || Dane Leblanc || Y || None
|-
| Cisco || VPNaaS - Driver || Dane Leblanc || Y || None
|-
| Embrane || Plugin || Ignacio Scopetta || N || No CI in place. Candidate to be removed from Neutron
|-
| Embrane || LBaaS - Driver || Ignacio Scopetta || N || No CI in place. Candidate to be removed from Neutron
|-
| Freescale || ML2 - Driver || Trinath Somanchi || - || Needs to be verified
|-
| Freescale || FWaaS - Driver || Trinath Somanchi || - || Needs to be verified
|-
| IBM || Plugin - SDN-VE || Mohammad Banikazemi || - || Results are not clear. Need clarification from IBM
|-
| Juniper || Plugin - Contrail || Rudra Rugge || Y || Needs to start testing all Neutron commits. Plugins just got merged in Juno-3
|-
| Mellanox || Plugin || Omri Marcovitch || N || It is deprecated. Will be removed in Kilo
|-
| Mellanox || ML2 - Driver || Omri Marcovitch || Y || None
|-
| Mellanox || ML2 - Sriovnic switch || Omri Marcovitch || N || Not working
|-
| Metaplugin || Plugin - Multiple || NTT Team || N || It is missing some Neutron commits
|-
| Midokura || Plugin - Midonet || Lucas Eznarriaga || Y || None
|-
| NEC || Plugin - OpenFlow || Akihiro Motoki || Y || None
|-
| Citrix NetScaler || LBaaS - Driver || Parikshit Manur || Y || Only testing LBaaS changes
|-
| Nuage Networks || Plugin - VSP || Franck Yelles || Y || Plugin behaving correctly for +1, manual -1
|-
| OFAgent || ML2 - OF || Yamamoto Takashi || Y || None
|-
| One Convergence || Plugin - NVSD || Hemanth Ravi || N || Logs are not available. It is missing some Neutron commits. Needs clarification
|-
| OpenDaylight || ML2 - ODL || ? || - || It is missing some Neutron commits
|-
| PLUMgrid || Plugin - Director || Fawad Khaliq || Y || None
|-
| Ryu || Plugin - Ryu Controller || Yamamoto Takashi || - || It is been deprecated and It will be removed in Kilo
|-
| Radware || LBaaS - Driver || Samuel Bercovici || N || CI does not exist. Should be removed from Neutron
|-
| Tail-f NCS || ML2 - NCS || Luke Gorrie || - || It is missing some Neutron commits
|-
| vArmour || FWaaS || Gary Duan || N || CI does not exist. Should be removed from Neutron
|-
| VMware || Plugin - NSX || Aaron Rosen || - || It is missing some Neutron commits.
|}

ThirdPartySystems/One Convergence CI

2014-08-18T18:50:02Z

Hemanthravi:

{{ThirdPartySystemInfo|name=One Convergence CI
|account=oneconvergence
|contact=Kedar Kulkarni<kedar.kulkarni@oneconvergence.com>, Deepak Gupta<deepak.gupta@oneconvergence.com>, Hemanth Ravi<hemanth.ravi@oneconvergence.com>
|intent=Testing neutron changes with One Convergence Plugin
|structure=Gerrit, Jenkins, Devstack, Tempest
|method=Gerrit to trigger Jenkins builds using Devstack on the latest Neutron patchset
|programs=Devstack, Neutron
|status=testing, non-voting}}

Neutron Plugins and Drivers

2014-08-18T18:46:01Z

Hemanthravi: /* Existing Plugin and Drivers */

=== Introduction ===
Ensuring release quality through proper testing is an important tenant of the OpenStack community and Neutron team wants to do our part. We are introducing changes below provide more visibility into the quality and stability of vendor plugin and driver code. The policies described here are in effect immediately.

=== Rationale ===
Code proposals for third party plugins have always presented a review challenge for the Neutron core team. In the early days, code was often proposed by core project contributors and our review process only validated whether the requirements were met for community coding style and unit testing. As Neutron has added new resources via extensions, it has become more difficult for Neutron reviewers to ensure the proposed code is functional. Many of the plugins and/or drivers require proprietary hardware and/or software to conduct such testing.

In addition to testing changes, the Neutron team is revising the requirements for the point of contact for third party code. The changes bring the written expectations for contacts in line with current practice.

=== Point of Contact Requirements ===
Each third party plugin and/or driver shall designate a point of contact for each coordinated release cycle. The contact will serve as a liaison between the Neutron core team and the vendor or community supporting the plugin or driver. The contact shall:

* Attend weekly Neutron team IRC meetings
* Be an active reviewer and contributor
* Be an active participant on openstack-dev mailing list
* Assist the core team with triaging bugs specific to the plugin and/or driver
* Ensure OpenStack development deadlines are properly communicated back to their company and/or community

NOTE: The this information can be maintained here: https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers

=== Testing Requirements ===
To be designated as compatible, a third-party plugin and/or driver code must implement external third party testing. The testing should be Tempest executed against a Devstack build with the proposed code changes. The environment managed by the vendor should be configured to incorporate the plugin and/or driver solution. The OpenStack Infrastructure team has provided details on how to integrate 3rd party testing at:

http://ci.openstack.org/third_party.html

and Tempest can be found at:

https://github.com/openstack/tempest

The Neutron team expects that the third party testing will provide a +/-1 verify vote for all changes to a plugin or driver’s code. In addition, the Neutron team expects that the third party test will also vote on all code submissions by the jenkins user. The jenkins user regularly submits requirements changes and the Neutron team hopes to catch any possible regressions as early as possible.

=== Existing Plugin and Drivers ===
Plugins and drivers currently in the Neutron project repository will be given a grace period until the Icehouse-2 milestone to implement external third party testing. At that time, the Neutron team will release a list of the compatible plugins and drivers (i.e. those that meet the testing requirements). Plugins and drivers that do not have external testing will be deprecated at the Icehouse release and will be candidates for removal when the J-release cycle opens.

{| class="wikitable"
|-
! Vendor !! Plugin/Driver Name !! Contact Name !! Status !! Notes
|-
| Neutron Team || ML2 - OVS/LB || Infra Team || Y || Covered by Infra (Jenkins)
|-
| A10 Networks || LBaaS Driver || Doug Wiegley || Y || None
|-
| Arista Networks || ML2 Driver || Sukhdev Kapur || Y || None
|-
| Big Switch || Plugin || Kevin Benton || Y || 8.5 hour delay
|-
| Big Switch || ML2 Driver || Kevin Benton || Y || 8.5 hour delay
|-
| Brocade || Vyatta Plugin || Karthik Natarajan || N || Only found logs for ML2. Needs clarification from Brocade
|-
| Brocade || ML2 Driver || Shiv Haris || Y || None
|-
| Cisco || Plugin - NXOS || Dane Leblanc || N || It will be removed in Juno
|-
| Cisco || Plugin - N1Kv || Dane Leblanc || Y || None
|-
| Cisco || ML2 - APIC || Dane Leblanc || N || It is not running against all Neutron commits, results are fake
|-
| Cisco || ML2 - DFA || Dane Leblanc || N || Results are fake. Needs clarification from Cisco
|-
| Cisco || ML2 - NXOS || Dane Leblanc || Y || None
|-
| Cisco || VPNaaS - Driver || ? || Y || None
|-
| Embrane || Plugin || Ignacio Scopetta || N || No CI in place. Candidate to be removed from Neutron
|-
| Embrane || LBaaS - Driver || Ignacio Scopetta || N || No CI in place. Candidate to be removed from Neutron
|-
| IBM || Plugin - SDN-VE || Mohammad Banikazemi || - || Results are not clear. Need clarification from IBM
|-
| Juniper || Plugin - Contrail || Rudra Rugge || Y || Needs to start testing all Neutron commits. Plugins just got merged in Juno-3
|-
| Mellanox || Plugin || Irena Berezovsky || N || It is deprecated. Will be removed in Kilo
|-
| Mellanox || ML2 - Driver || Irena Berezovsky || N || Logs are not available. Needs clarification
|-
| Mellanox || ML2 - Sriovnicagent || Irena Berezovsky || N || Logs are not available. Needs clarification
|-
| Metaplugin || Plugin - Multiple || NTT Team || N || It is missing some Neutron commits
|-
| Midokura || Plugin - Midonet || Lucas Eznarriaga || Y || None
|-
| NEC || Plugin - OpenFlow || Akihiro Motoki || Y || None
|-
| Nuage Networks || Plugin - VSP || Franck Yelles || Y || Plugin behaving correctly for +1, manual -1
|-
| OFAgent || ML2 - OF || Yamamoto Takashi || Y || None
|-
| OneCoverage || Plugin - NVSD || Hemanth Ravi || N || Logs are not available. It is missing some Neutron commits. Needs clarification
|-
| OpenDaylight || ML2 - ODL || ? || - || It is missing some Neutron commits
|-
| PLUMgrid || Plugin - Director || Fawad Khaliq || Y || None
|-
| Ryu || Plugin - Ryu Controller || Yamamoto Takashi || - || It is been deprecated and It will be removed in Kilo
|-
| Radware || LBaaS - Driver || Samuel Bercovici || N || CI does not exist. Should be removed from Neutron
|-
| Tail-f NCS || ML2 - NCS || Luke Gorrie || - || It is missing some Neutron commits
|-
| vArmour || FWaaS || Gary Duan || N || CI does not exist. Should be removed from Neutron
|-
| VMware || Plugin - NSX || Aaron Rosen || - || It is missing some Neutron commits.
|}