Jump to: navigation, search

Difference between revisions of "Teams"

Line 1: Line 1:
 
__NOTOC__
 
__NOTOC__
 
= Teams =
 
= Teams =
 
 
Teams are groups of people sharing a common interest for a task or code subsystem in OpenStack.
 
Teams are groups of people sharing a common interest for a task or code subsystem in OpenStack.
  
Line 7: Line 6:
  
 
== Horizontal teams ==
 
== Horizontal teams ==
 
 
Those teams work on a task that is common to every [[OpenStack]] core project.
 
Those teams work on a task that is common to every [[OpenStack]] core project.
  
Line 15: Line 13:
  
 
=== Docs team ===
 
=== Docs team ===
 
 
* Launchpad team: http://launchpad.net/~openstack-doc
 
* Launchpad team: http://launchpad.net/~openstack-doc
 
* Meeting:  [[Meetings/DocTeamMeeting|Doc Team meeting]]
 
* Meeting:  [[Meetings/DocTeamMeeting|Doc Team meeting]]
Line 28: Line 25:
  
 
== Nova subteams ==
 
== Nova subteams ==
 
 
=== Nova API Team ===
 
=== Nova API Team ===
 
All things api related, with special focus on additional features and cleanup of the openstack api.
 
All things api related, with special focus on additional features and cleanup of the openstack api.
 +
 
* https://launchpad.net/~nova-api
 
* https://launchpad.net/~nova-api
 
* lead - bcwaldon
 
* lead - bcwaldon
Line 36: Line 33:
 
=== Nova Database Team ===
 
=== Nova Database Team ===
 
Cleanup of the db layer, DB testing, alternative backends
 
Cleanup of the db layer, DB testing, alternative backends
 +
 
* https://launchpad.net/~nova-database
 
* https://launchpad.net/~nova-database
 
* lead - _0x44 (unconfirmed)
 
* lead - _0x44 (unconfirmed)
Line 41: Line 39:
 
=== Nova Scaling Team ===
 
=== Nova Scaling Team ===
 
Distributed zones, aggregation, geographically diverse zones.
 
Distributed zones, aggregation, geographically diverse zones.
 +
 
* https://launchpad.net/~nova-scaling
 
* https://launchpad.net/~nova-scaling
 
* lead - comstud
 
* lead - comstud
Line 46: Line 45:
 
=== Nova Orchestration Team ===
 
=== Nova Orchestration Team ===
 
Orchestration, workflow management for requests, state machine for recovery
 
Orchestration, workflow management for requests, state machine for recovery
 +
 
* https://launchpad.net/~nova-orchestration
 
* https://launchpad.net/~nova-orchestration
 
* lead - sandywalsh
 
* lead - sandywalsh
Line 51: Line 51:
 
=== Nova Upgrades Team ===
 
=== Nova Upgrades Team ===
 
Seamless upgrades for nova.  Some research and planning still needs to be done here.
 
Seamless upgrades for nova.  Some research and planning still needs to be done here.
 +
 
* https://launchpad.net/~nova-upgrades
 
* https://launchpad.net/~nova-upgrades
 
* lead -rjh
 
* lead -rjh
Line 56: Line 57:
 
=== Nova Feature Parity Team ===
 
=== Nova Feature Parity Team ===
 
Full feature parity for xenapi and libvirt/kvm. Includes user facing parity issues like common images.
 
Full feature parity for xenapi and libvirt/kvm. Includes user facing parity issues like common images.
 +
 
* https://launchpad.net/~nova-feature-parity
 
* https://launchpad.net/~nova-feature-parity
 
* lead - sleepsonthefloor
 
* lead - sleepsonthefloor
Line 61: Line 63:
 
=== Openstack Volumes Team ===
 
=== Openstack Volumes Team ===
 
Volumes api, drivers, scheduling, zone support.
 
Volumes api, drivers, scheduling, zone support.
 +
 
* https://launchpad.net/~openstack-volume
 
* https://launchpad.net/~openstack-volume
 
* lead - renuka
 
* lead - renuka
Line 66: Line 69:
 
=== Nova Auth Team ===
 
=== 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.
 
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.
 +
 
* https://launchpad.net/~nova-auth
 
* https://launchpad.net/~nova-auth
 
* lead - vishy
 
* lead - vishy
Line 71: Line 75:
 
=== Nova Security Improvements Team ===
 
=== 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.
 
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.
 +
 
* https://launchpad.net/~nova-security-improvements Security
 
* https://launchpad.net/~nova-security-improvements Security
 
* lead - rjh
 
* lead - rjh
Line 76: Line 81:
 
=== Nova Operational Support Team ===
 
=== Nova Operational Support Team ===
 
Collecting requirements from operational groups and generating tooling and admin apis for operations. This seems like a very important team, but I don't have someone to head it up yet.  Volunteers requested
 
Collecting requirements from operational groups and generating tooling and admin apis for operations. This seems like a very important team, but I don't have someone to head it up yet.  Volunteers requested
 +
 
* https://launchpad.net/~nova-operations
 
* https://launchpad.net/~nova-operations
 
* lead - (no lead yet)
 
* lead - (no lead yet)
Line 81: Line 87:
 
=== Nova Testing Cleanup Team ===
 
=== 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 and a lead.
 
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 and a lead.
 +
 
* https://launchpad.net/~nova-testing
 
* https://launchpad.net/~nova-testing
 
* lead - (no lead yet)
 
* lead - (no lead yet)
  
 
=== Nova Documentation Improvements Team ===
 
=== Nova Documentation Improvements Team ===
Clean up doc bugs, add to and improve existing Nova docs.  
+
Clean up doc bugs, add to and improve existing Nova docs.
 +
 
 
* https://launchpad.net/~nova-docs
 
* https://launchpad.net/~nova-docs
 
* lead - razique
 
* lead - razique
 +
 +
=== Nova Network Team ===
 +
Networking code/concerns and interaction of external network services with Nova.
 +
 +
* [https://launchpad.net/~nova-docs https://launchpad.net/~nova-network]
 +
* lead - tr3buchet

Revision as of 19:27, 25 October 2011

Teams

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

<<TableOfContents()>>

Horizontal teams

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

CI team

Docs team

QA team

Release team

Nova subteams

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 Upgrades Team

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

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 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.

Nova Operational Support Team

Collecting requirements from operational groups and generating tooling and admin apis for operations. This seems like a very important team, but I don't have someone to head it up yet. Volunteers requested

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 and a lead.

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.