Jump to: navigation, search


Revision as of 21:25, 24 November 2014 by Snaiksat (talk | contribs)

The number of sub teams in Neutron has grown to a crazy level. At some point in time, it made sense to have sub teams, but the sheer growth and lack of a clear charter for many of them has made their existence questionable. To solve this, sub teams should post a charter for each release explaining what they want to accomplish. The neutron-drivers team will then decide if it makes sense for a sub team to exist for that cycle. Ideally the sub teams own discovery process will lead to a decision on disbanding for a cycle in which there is no clear work direction and deliverable. An example of a functioning sub team which formed, accomplished work, and then disbanded was the Neutron DB sub team which worked for a few months during the Juno cycle.

Sub Team Charters

The existing NeutronSubTeams should put their charters below for evaluation in next week's neutron-drivers meeting.

An example of this charter is below.


This sub team does something really cool which everyone loves.

Charter for Kilo

Unicorns. With rainbows. So awesome.

Spec tracking

Put approved specs here.

FWaaS Team

Implement services and associated libraries that provide cloud-centric abstractions for a security feature set spanning traditional L2/3 firewalls to richer application-aware next-generation firewalls.

Charter for Kilo

The FWaaS sub team coordinates the evolution of the FWaaS advanced service plugin and drivers (both, reference implementation, and vendor-specific). Authors and maintainers of all FWaaS service plugins and drivers are encouraged to participate, along with everyone in the OpenStack community who has an interest in improving the FWaaS component.

  • Coordinate FWaaS with any Neutron-wide REST front-end and plugin API refactoring efforts
  • Coordinate FWaaS with any Neutron-wide improvements in core DB layer (replace locking with optimistic/retry approaches, eliminate mix-ins,...)
  • Coordinate with the rest of the Advanced Services' team to support any common services' framework and split-related efforts
  • Evolve default firewall insertion model which attaches a firewall to all tenant routers, to one that can do this in a more granular fashion
  • Introduce Service Objects and Service Groups feature
  • Support addition of Vendor FWaaS plugins and drivers
  • Maintain and support FWaaS code-base from prior releases

Spec tracking

https://review.openstack.org/#/c/131596 (others to be added shortly)

LBaaS Team

Design, development, and merging of LBaaS v2 functionality.

Charter for Kilo

Merging changes to feature branch, agent-ified reference driver, CLI changes. With rainbows.

Spec tracking

To be re-proposed for Kilo soon: