Features/Eucalyptus

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
m (Detailed Description)
(Detailed Description)
 
(14 intermediate revisions by 5 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/17 |Fedora 17]]  
+
* Targeted release: [[Releases/18 |Fedora 18]]  
* Last updated: 2011-11-18
+
* Last updated: 2012-10-22
* Percentage of completion: 10%
+
* 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.1 of all of the major components of Eucalyptus:
+
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.)
- Storage Controller (analogous to EBS)
+
* Storage Controller (analogous to EBS)
- Walrus (analogous to S3)
+
* Walrus (analogous to S3)
- 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 does 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.
+
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 ==
  
TODO
+
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 [http://agrimmsreality.blogspot.com/2012/01/configuring-eucalyptus-3-devel.html 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 [https://projects.eucalyptus.com/redmine/projects/eustore/ Eustore]
 +
 
 +
4) Possibly run through various automated test cases using the [https://github.com/eucalyptus/eutester Eutester framework]
  
 
== User Experience ==
 
== User Experience ==
  
Users will have the ability to build an IaaS system.
+
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 ==
 
== Dependencies ==
Line 53: Line 73:
 
* HA-JDBC  
 
* HA-JDBC  
 
* Hibernate
 
* Hibernate
* JasperReports
+
* JasperReports (optional)
 
* Mule
 
* Mule
 
* Spring
 
* Spring
Line 61: Line 81:
 
== Contingency Plan ==
 
== Contingency Plan ==
  
We would punt to F18.
+
We would punt to F19.
  
 
== Documentation ==
 
== Documentation ==
Line 70: Line 90:
 
== Release Notes ==
 
== Release Notes ==
  
TODO
+
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.
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
 
* See [[Talk:Features/Eucalyptus]]
 
* See [[Talk:Features/Eucalyptus]]
 
  
 
[[Category:Cloud SIG]]
 
[[Category:Cloud SIG]]
[[Category:FeaturePageIncomplete]]
+
[[Category:FeatureAcceptedF18]]

Latest revision as of 16:26, 13 December 2012

Contents

[edit] Eucalyptus

[edit] 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.

[edit] Owners

[edit] Current status

[edit] 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.

[edit] Benefit to Fedora

Fedora can be used to build a highly available and scalable AWS-compatible compute/storage cloud.

[edit] 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.

[edit] 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

[edit] 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.

[edit] 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)

[edit] Contingency Plan

We would punt to F19.

[edit] Documentation

[edit] 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.

[edit] Comments and Discussion