Difference between revisions of "NovaLieutenants"
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
= Rationale = | = Rationale = | ||
| − | |||
The number of people contributing code to nova has grown dramatically over the last few months, and it is becoming difficult to maintain a clear picture of the entire code base. We are attempting to move towards a somewhat more sectioned view of the code, where there is at least one person who is responsible for maintaining a given section of code. This is similar to [http://p2pfoundation.net/Linux_-_Governance#Linux_Organization the process] used for linux development. | The number of people contributing code to nova has grown dramatically over the last few months, and it is becoming difficult to maintain a clear picture of the entire code base. We are attempting to move towards a somewhat more sectioned view of the code, where there is at least one person who is responsible for maintaining a given section of code. This is similar to [http://p2pfoundation.net/Linux_-_Governance#Linux_Organization the process] used for linux development. | ||
= Lieutenants = | = Lieutenants = | ||
| − | |||
{| border="1" cellpadding="2" cellspacing="0" | {| border="1" cellpadding="2" cellspacing="0" | ||
| − | | | + | | '''What''' |
|- | |- | ||
| − | | | + | | [[OpenStack]] API |
|- | |- | ||
| − | | | + | | AWS API |
|- | |- | ||
| − | | | + | | Network Service |
|- | |- | ||
| − | | | + | | Compute Service |
|- | |- | ||
| − | | | + | | Volume Service |
|- | |- | ||
| − | | | + | | Scheduler Service <<BR>> (including zones) |
|- | |- | ||
| − | | | + | | Libvirt Driver |
|- | |- | ||
| − | | | + | | Xen Driver |
|- | |- | ||
| − | | | + | | VMWare Driver |
|- | |- | ||
| − | | | + | | HyperV Driver |
|- | |- | ||
| − | | | + | | Testing |
|- | |- | ||
| − | | | + | | Documentation |
|- | |- | ||
| − | | | + | | Billing / Usage |
|- | |- | ||
| − | | | + | | Monitoring |
|- | |- | ||
| − | | | + | | Scalability/Performance <<BR>> (dealing with issues <<BR>> like fakevirt & how to simulate <<BR>> thousands of nodes on "small" clusters) |
|- | |- | ||
| − | | | + | | Admin API |
|- | |- | ||
| − | | | + | | Deployment (chef / puppet) |
|- | |- | ||
| − | | | + | | Ubuntu packaging |
|- | |- | ||
| − | | | + | | RHEL packaging |
|- | |- | ||
| − | | | + | | OpenSuSE/SLES packaging |
Revision as of 14:29, 4 May 2011
Rationale
The number of people contributing code to nova has grown dramatically over the last few months, and it is becoming difficult to maintain a clear picture of the entire code base. We are attempting to move towards a somewhat more sectioned view of the code, where there is at least one person who is responsible for maintaining a given section of code. This is similar to the process used for linux development.
Lieutenants
| What |
| OpenStack API |
| AWS API |
| Network Service |
| Compute Service |
| Volume Service |
| Scheduler Service < > (including zones) |
| Libvirt Driver |
| Xen Driver |
| VMWare Driver |
| HyperV Driver |
| Testing |
| Documentation |
| Billing / Usage |
| Monitoring |
| Scalability/Performance < > (dealing with issues < > like fakevirt & how to simulate < > thousands of nodes on "small" clusters) |
| Admin API |
| Deployment (chef / puppet) |
| Ubuntu packaging |
| RHEL packaging |
| OpenSuSE/SLES packaging |
