Jump to: navigation, search

Difference between revisions of "Obsolete:Neutron/Teams"

Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
−
= Quantum Teams =
+
Quantum uses a concept of "sub-teams" to help distribute the work of design reviews, bug triage, code reviews, progress updates, etc.   
−
== Quantum API team ==
 
−
This is team which looks after the Quantum API, and the plugin interface. This also includes the wsgi framework (for both core and extension APIs), the policy engine, and the authorization policies themselves. Members of this team should also ensure that plugin-specific API extensions respect the Quantum API guidelines.  Another important duty for this team is ensuring API changes are always backward compatible.
 
  
−
== Quantum DB team ==
+
Current Set of Quantum Teams:  
−
Main task: Managing data models, and the db_base_plugin. Striving towards efficient use of the db engine resources. Also looking after DB upgrades.
 
  
−
== Quantum DHCP team ==
+
Feel free to add yourself as a member of the team.  Being a team lead or member does not give any official authority beyond the respect they have already gained from the community.  It is more about distributing work and easing communication as people try to understand the state of the project in a particular area and to coordinate new work in an area.
−
Maintaining the DHCP agent and its drivers, which constitute the reference implementation of the Quantum DHCP service.
 
  
−
== Quantum L3 team ==
 
−
Maintaining the L3 agent, which is the reference implementation of Quantum L3 APIs
 
−
 
−
== Quantum Client team ==
 
−
Maintaining and evolving the client library in python-Quantumclient, and dealing with other openstack projects that use it (nova, horizon).
 
−
 
−
== Quantum CLI team ==
 
−
Maintaining and evolving the Quantum CLI.
 
−
 
−
== Quantum CI team ==
 
−
Ensuring Quantum has proper gates in place on Jenkins. This will involve devstack exercise in the first place, and tempest integration going forward. This is also the team that should interact with Openstack-CI team.
 
−
 
−
== Quantum Plugin teams ==
 
−
The goal of these teams is to ensure each plugin is always up-to-date and keeps working fine as Quantum evolves. Indeed even if the plugin interface is a well-defined interface, and basic code coverage is enforced through unit tests, breakage is always likely For information about leaders for specific plugins, please refer to the table below.
 
−
 
−
NOTE: As each dev is required to write unit tests for every new piece of code submitted into Quantum, there is no reason for a specific team looking after unit tests.
 
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
−
| Team  
+
| Team Name
−
| Team Members  
+
| Team Lead
 +
|  Team Members  
 +
|  tag
 
|-
 
|-
−
| API  
+
| API design & cohesiveness
−
| Salvatore Orlando, Bob Kukura
+
| salv-orlando
 +
|  salv-orlando, rkukura
 +
|  api
 
|-
 
|-
−
| DB  
+
| DB layer
−
| Salvatore Orlando
+
| markmcclain
 +
|  markmcclain
 +
|  db
 
|-
 
|-
−
| DHCP
+
| CLI & client
−
| Mark [[McClain]]
+
| gongysh
 +
|  gongysh, markmcclain
 
|-
 
|-
−
| L3
+
| System Test / Tempest integration
−
| Dan Wendlandt
+
| nachi
 +
|  nachi, maru
 
|-
 
|-
−
| Client
+
| Horizon + Quantum Integration
−
|   
+
|  amotoki
 +
|  amotoki, nachi
 
|-
 
|-
−
| CLI
+
| stable releases
−
| Yong Sheng Gong
+
| garyk
 +
|  garyk, danwent
 +
|  (folsom-backport-potential)
 
|-
 
|-
−
| CI
+
| Quantum + Nova Integration
−
|   
+
|  garyk
 +
|  garyk
 
|-
 
|-
−
| Open vSwitch Plugin
+
| L3 / IPAM / DHCP
−
| Bob Kukura
+
| markmcclain
 +
|  markmcclain, danwent, garyk
 +
|  l3-ipam-dhcp
 
|-
 
|-
−
| Linux Bridge Plugin
+
| Admin Docs
−
| Bob Kukura
+
| danwent
 +
|  danwent
 
|-
 
|-
−
| Cisco Plugin
+
| LBaaS
−
| Edgar Magana
+
| TBD
 +
|  pls add
 +
|  lb
 
|-
 
|-
−
| NEC Plugin
+
| Security Groups / FW
−
| Akihiro Motoki
+
| arosen
 +
|  arosen, amotoki
 +
|  sg-fw
 
|-
 
|-
−
| Nicira Plugin  
+
| VPN
−
| Aaron Rosen
+
|  markmcclain
 +
|  markmcclain
 +
|}
 +
 
 +
Core-team Plugin Contacts
 +
 
 +
{| border="1" cellpadding="2" cellspacing="0"
 +
|  Plugin Name
 +
|-
 +
|  OVS + LB
 +
|  ? rkukura?
 +
|  ovs or lb
 +
|-
 +
|  Cisco plugin
 +
| emagana
 
|-
 
|-
−
| Ryu Plugin  
+
| Nicira NVP Plugin
−
|   
+
|  arosen
−
|}
+
|  nicira
 +
|-
 +
|  Ryu Plugin  
 +
|  yamahata (non-core)
 +
|-
 +
| NEC plugin
 +
|  amotoki
 +
|  nec
 +
|-
 +
|  Meta plugin
 +
|  nachi (non-core)
 +
|  meta

Revision as of 20:46, 12 November 2012

Quantum uses a concept of "sub-teams" to help distribute the work of design reviews, bug triage, code reviews, progress updates, etc.

Current Set of Quantum Teams:

Feel free to add yourself as a member of the team. Being a team lead or member does not give any official authority beyond the respect they have already gained from the community. It is more about distributing work and easing communication as people try to understand the state of the project in a particular area and to coordinate new work in an area.

Team Name Team Lead Team Members tag
API design & cohesiveness salv-orlando salv-orlando, rkukura api
DB layer markmcclain markmcclain db
CLI & client gongysh gongysh, markmcclain
System Test / Tempest integration nachi nachi, maru
Horizon + Quantum Integration amotoki amotoki, nachi
stable releases garyk garyk, danwent (folsom-backport-potential)
Quantum + Nova Integration garyk garyk
L3 / IPAM / DHCP markmcclain markmcclain, danwent, garyk l3-ipam-dhcp
Admin Docs danwent danwent
LBaaS TBD pls add lb
Security Groups / FW arosen arosen, amotoki sg-fw
VPN markmcclain markmcclain

Core-team Plugin Contacts

Plugin Name
OVS + LB  ? rkukura? ovs or lb
Cisco plugin emagana
Nicira NVP Plugin arosen nicira
Ryu Plugin yamahata (non-core)
NEC plugin amotoki nec
Meta plugin nachi (non-core) meta
Retrieved from "https://wiki.openstack.org/w/index.php?title=Obsolete:Neutron/Teams&oldid=1008"