Jump to: navigation, search


Revision as of 20:09, 21 May 2014 by Mestery (talk | contribs) (Core Members)

This page tracks all policies and procedures for working within the OpenStack Neutron Project.


The Neutron team uses the neutron-specs repository for it's specification reviews. Detailed information on the process is found here.


Code Reviews

Contributor Onboarding

Core Members

The Neutron Core Team is responsible for merging changes into the following repositories:

While everyone is encouraged to review changes for these repositories, neutron-core has the ability to +2/-2, as well as +A changes to these repositories.

Adding or Removing Members

A new member to neutroin-core may be proposed at any time to the openstack-dev mailing list. Typically the PTL will propose a new member after discussions with the core team. Once a proposal has been made, five existing neutron-core members must respond to the email with a +1. Another neutron-core member can vote -1 to veto the nomination of the proposed core team member.

The PTL may remove a member from neutron-core at any time. Typically when a member has decreased their involvement with the project through a drop in reviews and participation in general project development, the PTL will propose their removal and remove them. Members who have previously been core may be fast-tracked back into core if their involvement picks back up.

Membership Expectations

Members of neutron-core have the following expectations:

  • Attendance at the weekly Neutron meeting on IRC.
  • Participation in neutron discussions on the mailing list, as well as in-channel in #openstack-neutron.
  • Participation in neutron related design summit sessions at the summits.

In addition to the above, code reviews are a critical. Neutron follows the documented OpenStack code review guidelines. We encourage all people to review neutron patches, but cores are required to maintain a level of review numbers relatively close to other cores. There are no hard statistics around code review numbers, but in general we use 30, 60, and 90 day stats when examining review stats:

There are soft-touch items around being a core as well. Gaining trust with the existing core team is important. Being able to work together with the existing team is critical as well. Being a core means spending a significant amount of time with the existing core team on IRC, the mailing list, and reviews. Ensuring you participate and engage here is critical to becoming a core.

Gate Failure Triage

Sub Teams

This is a list of the currently operating Neutron sub-teams. If you would like to form a new Neutron sub-team, please attend our weekly meeting and propose your team there. You can also send out an email to the openstack-dev mailing list. If a sub-team has completed it's work and has wound down, these will be removed from the list below.

Sub-team Lead Name and IRC handle Meeting Page Status Page
Advanced Services Sumit Naiksatam (snaiksat) https://wiki.openstack.org/wiki/Meetings/AdvancedServices
DB Migrations Henry Gessau (HenryG) https://wiki.openstack.org/wiki/Meetings/NeutronDB
Distributed Virtual Router (DVR) Swaminathan Vasudevan (Swami) https://wiki.openstack.org/wiki/Meetings/Distributed-Virtual-Router
FWaaS Sumit Naiksatam (snaiksat) https://wiki.openstack.org/wiki/Meetings/FWaaS
Group-Based Policy Sumit Naiksatam (snaiksat) https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy
IPv6 Sean Collins (sc68cal) https://wiki.openstack.org/wiki/Meetings/Neutron-IPv6-Subteam
L3 Carl Baldwin (carl_baldwin) https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam
LBaaS Kyle Mestery (mestery) https://wiki.openstack.org/wiki/Network/LBaaS
ML2 Robert Kukue (rkukura) and Sukhdev Kapur (Suhkdev) https://wiki.openstack.org/wiki/Meetings/ML2
nova-network parity Mark McClain (markmcclain)
QoS Sean Collins (sc68cal)

Third Party Testing