Jump to: navigation, search


Revision as of 20:48, 16 February 2013 by Fungi (talk | contribs) (import errors)


Teams are groups of people sharing a common interest for a task or code subsystem in OpenStack.

Horizontal teams

Those teams work on a task that is common to every OpenStack core project.

CI team

Docs team

QA team

Release team

Stable Branch Maintenance Team

Community team

Vulnerability Management team

Nova subteams

Rather than using different mailing lists for every team, please post to the mailing normal openstack mailing list with the shortname for the team in the subject. For example:

[API] Adding new extensions

Nova API Team

All things api related, with special focus on additional features and cleanup of the openstack api.

Nova Database Team

Cleanup of the db layer, DB testing, alternative backends

Nova Scaling Team

Distributed zones, aggregation, geographically diverse zones.

Nova Orchestration Team

Orchestration, workflow management for requests, state machine for recovery

Nova Feature Parity Team

Full feature parity for xenapi and libvirt/kvm. Includes user facing parity issues like common images.

Openstack Volumes Team

Volumes api, drivers, scheduling, zone support.

Nova Testing Cleanup Team

We have discussed cleaning up the unit tests and separating out integration tests for a while, but this needs a specific team to focus on it. We need volunteers to help.

Nova Documentation Improvements Team

Clean up doc bugs, add to and improve existing Nova docs.

Nova Network Team

Networking code/concerns and interaction of external network services with Nova.

Nova EC2 API Team

EC2 API Features, bugs, and testing

Nova Operational Support Team

Collecting requirements from operational groups and generating tooling and admin apis for operations.

Nova Tenative Subteams

These teams are desired but don't have enough activity yet to be official teams

Nova Upgrades Team

Seamless upgrades for nova. Some research and planning still needs to be done here.

Nova Auth Team

Code for Authorization checking in nova and integration with Keystone. Planning is pretty much done here, but it will touch a lot of the code, so we could use a few people focusing on it. Team is primarily to help collect volunteers.

Nova Security Improvements Team

Planning for security improvements to nova. Due to the large number of code changes being worked on in essex, we aren't planning on locking things down completely in the next six months. This will likely be mostly planning in the essex time frame, with actual implementations to hit in F.