(Moved to FeatureAcceptedF17 - feature was accepted at 2012-01-30 meeting.) |
|||
| (7 intermediate revisions by 4 users not shown) | |||
| Line 9: | Line 9: | ||
* Name: [[User:arg|Andy Grimm]] | * Name: [[User:arg|Andy Grimm]] | ||
* Email: [mailto:agrimm@gmail.com agrimm@gmail.com] | * Email: [mailto:agrimm@gmail.com agrimm@gmail.com] | ||
* Name: [[User:Madsa|Matt Spaulding]] | |||
* Email: [mailto:mspaulding06@gmail.com mspaulding06@gmail.com] | |||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/18 |Fedora 18]] | ||
* Last updated: | * Last updated: 2012-10-22 | ||
* Percentage of completion: | * Current Progress: [https://eucalyptus.atlassian.net/browse/EUCA-2578 Fedora Inclusion Tasks] | ||
* Percentage of completion: 100% | |||
== Detailed Description == | == Detailed Description == | ||
This feature would include version 3. | This feature would include version 3.2 of all of the major components of Eucalyptus: | ||
* Cloud Controller (The central web service stack, web UI, account management, etc.) | * Cloud Controller (The central web service stack, web UI, account management, etc.) | ||
| Line 25: | Line 29: | ||
* Cluster Controller (analogous to EC2) | * Cluster Controller (analogous to EC2) | ||
* Node Controller (which manages the hypervisor on individual compute nodes in a cluster) | * Node Controller (which manages the hypervisor on individual compute nodes in a cluster) | ||
It also includes the new web-based User Console for managing cloud resources. | |||
Eucalyptus works with either Xen or KVM, and can use openldap for account management. | Eucalyptus works with either Xen or KVM, and can use openldap for account management. | ||
| Line 34: | Line 40: | ||
== Scope == | == Scope == | ||
The main challenge is in packaging a large number of Java dependencies. There is a list of direct dependencies at [[Eucalyptus]], but it does | The main challenge is in packaging a large number of Java dependencies. There is a list of direct dependencies at [[Eucalyptus]], but it does not contain all transitive build dependencies yet. There will also be some distro integration work, but much of this is happening as part of the upstream packaging and release process. | ||
== How To Test == | == How To Test == | ||
| Line 75: | Line 81: | ||
== Contingency Plan == | == Contingency Plan == | ||
We would punt to | We would punt to F19. | ||
== Documentation == | == Documentation == | ||
| Line 90: | Line 96: | ||
[[Category:Cloud SIG]] | [[Category:Cloud SIG]] | ||
[[Category: | [[Category:FeatureAcceptedF18]] | ||
Latest revision as of 16:26, 13 December 2012
Eucalyptus
Summary
Eucalyptus is a cloud computing software platform for on-premise (private) Infrastructure as a Service clouds. It uses existing infrastructure to create scalable and secure AWS-compatible cloud resources for compute, network and storage.
Owners
- Name: Andy Grimm
- Email: agrimm@gmail.com
- Name: Matt Spaulding
- Email: mspaulding06@gmail.com
Current status
- Targeted release: Fedora 18
- Last updated: 2012-10-22
- Current Progress: Fedora Inclusion Tasks
- Percentage of completion: 100%
Detailed Description
This feature would include version 3.2 of all of the major components of Eucalyptus:
- Cloud Controller (The central web service stack, web UI, account management, etc.)
- Storage Controller (analogous to EBS)
- Walrus (analogous to S3)
- Cluster Controller (analogous to EC2)
- Node Controller (which manages the hypervisor on individual compute nodes in a cluster)
It also includes the new web-based User Console for managing cloud resources.
Eucalyptus works with either Xen or KVM, and can use openldap for account management.
Benefit to Fedora
Fedora can be used to build a highly available and scalable AWS-compatible compute/storage cloud.
Scope
The main challenge is in packaging a large number of Java dependencies. There is a list of direct dependencies at Eucalyptus, but it does not contain all transitive build dependencies yet. There will also be some distro integration work, but much of this is happening as part of the upstream packaging and release process.
How To Test
1) Install the following packages:
eucalyptus-cloud eucalyptus-sc eucalyptus-nc eucalyptus-cc eucalyptus-walrus
The configuration will default to "SYSTEM" mode for networking, which would allow a single node configuration to work for test purposes.
2) component configuration and registration will mostly follow my blog post from 1/19, though we may script a simpler process for this.
3) Test image launching either with boxgrinder-generated images or with images from Eustore
4) Possibly run through various automated test cases using the Eutester framework
User Experience
Users will have the ability to build an Amazon-compatible cloud and use tools such as boto, euca2ools, BoxGrinder, HybridFox, etc. to manage compute instances and storage.
Dependencies
Briefly:
- ActiveMQ
- Axiom
- Google Web Toolkit
- HA-JDBC
- Hibernate
- JasperReports (optional)
- Mule
- Spring
- Axis2c
- WSDL2C (from Axis2/Java, but may be separated into a fragment package, as Axis2/Java has a huge dependency list)
Contingency Plan
We would punt to F19.
Documentation
Release Notes
Eucalyptus is an AWS-compatible cloud which allows users to manage compute and storage resources in a private cloud using the same tools and APIs as are used with AWS.