Difference between revisions of "NeutronSubteamCharters"
Line 11: | Line 11: | ||
==== Spec tracking ==== | ==== Spec tracking ==== | ||
Put approved specs here. | Put approved specs here. | ||
+ | |||
+ | === Advanced Services Team === | ||
+ | Implement services and associated libraries that provide abstractions for advanced network functions beyond basic L2/L3 connectivity and forwarding.. | ||
+ | ==== Charter for Kilo ==== | ||
+ | The Advanced Services' team coordinates the evolution of the advanced services' plugins and drivers (both, reference implementation, and vendor-specific). Authors and maintainers of all service plugins and drivers are encouraged to participate, along with everyone in the OpenStack community who has an interest in improving advanced networking services. | ||
+ | * Coordinate with any Neutron-wide REST front-end and plugin API refactoring efforts | ||
+ | * Coordinate with any Neutron-wide improvements in core DB layer (replace locking with optimistic/retry approaches, eliminate mix-ins,...) | ||
+ | * Coordinate with advanced services' framework and split-related efforts | ||
+ | * Participate in the L3 agent refactoring that impacts advanced services' drivers | ||
+ | ==== Spec tracking ==== | ||
+ | Adv Services split: https://review.openstack.org/136835 | ||
+ | (others to be added shortly) | ||
=== FWaaS Team === | === 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. | 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 ==== | ==== Charter for Kilo ==== | ||
− | The FWaaS | + | The FWaaS 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 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 FWaaS with any Neutron-wide improvements in core DB layer (replace locking with optimistic/retry approaches, eliminate mix-ins,...) | ||
Line 24: | Line 36: | ||
* Maintain and support FWaaS code-base from prior releases | * Maintain and support FWaaS code-base from prior releases | ||
==== Spec tracking ==== | ==== Spec tracking ==== | ||
− | https://review.openstack.org/#/c/131596 | + | Service Groups and Objects: https://review.openstack.org/#/c/131596 |
(others to be added shortly) | (others to be added shortly) | ||
Revision as of 21:31, 24 November 2014
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.
Contents
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.
MySubTeam
This sub team does something really cool which everyone loves.
Charter for Kilo
Unicorns. With rainbows. So awesome.
Spec tracking
Put approved specs here.
Advanced Services Team
Implement services and associated libraries that provide abstractions for advanced network functions beyond basic L2/L3 connectivity and forwarding..
Charter for Kilo
The Advanced Services' team coordinates the evolution of the advanced services' plugins and drivers (both, reference implementation, and vendor-specific). Authors and maintainers of all service plugins and drivers are encouraged to participate, along with everyone in the OpenStack community who has an interest in improving advanced networking services.
- Coordinate with any Neutron-wide REST front-end and plugin API refactoring efforts
- Coordinate with any Neutron-wide improvements in core DB layer (replace locking with optimistic/retry approaches, eliminate mix-ins,...)
- Coordinate with advanced services' framework and split-related efforts
- Participate in the L3 agent refactoring that impacts advanced services' drivers
Spec tracking
Adv Services split: https://review.openstack.org/136835 (others to be added shortly)
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 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
Service Groups and Objects: 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:
http://git.openstack.org/cgit/openstack/neutron-specs/tree/specs/juno-incubator