Difference between revisions of "Nova"
| Line 3: | Line 3: | ||
The purpose of this document is to capture the pluses and minuses of using Nova's code as a part of Cloud servers v2 | The purpose of this document is to capture the pluses and minuses of using Nova's code as a part of Cloud servers v2 | ||
| − | Plus | + | === Plus === |
* Scalable architecture | * Scalable architecture | ||
* Many months ahead of us | * Many months ahead of us | ||
| + | * written in Python | ||
| + | * open source and it appears that they will be following an open development model | ||
| − | Minus | + | === Minus === |
| + | * Closely tied to Eucalyptus' technical decision. i.e. AOE, heavy use of vlans | ||
| + | * Missing large portions of functionality needed by hosting providers, i.e. metrics and billing. | ||
| + | * Only supports AMI's | ||
Revision as of 16:02, 8 June 2010
Nova Cloud Review
The purpose of this document is to capture the pluses and minuses of using Nova's code as a part of Cloud servers v2
Plus
- Scalable architecture
- Many months ahead of us
- written in Python
- open source and it appears that they will be following an open development model
Minus
- Closely tied to Eucalyptus' technical decision. i.e. AOE, heavy use of vlans
- Missing large portions of functionality needed by hosting providers, i.e. metrics and billing.
- Only supports AMI's
