Difference between revisions of "Template:FedCloudUseCases"
Jump to navigation
Jump to search
Line 9: | Line 9: | ||
== Short Description == | == Short Description == | ||
{{{ShortDesc | Short description of the FedCloud Use Case}}} | {{{ShortDesc | Short description of the FedCloud Use Case.}}} | ||
== Tasks == | == Tasks == |
Revision as of 15:47, 9 October 2012
General Information
- Status: planned, active, completed
- Start Date: DD/MM/YY
- End Date: DD/MM/YY
- EGI.eu contact: contact@egi.eu
- External contact: contact@something
Short Description
Short description of the FedCloud Use Case.
Tasks
Use case 1: the ability to upload and start a prepared VMware VM. The VM only has to be able to make outbound connections: to Amazon's SQS for job info, to HBase cluster to retrieve and store data, and to the peachnote server to regularly update the workflow code. No inbound connections are needed, which hopefully means less administrative and security concerns.
- Choose and obtain access to site(s) of the EGI Federated Cloud testbed
- Convert the Peachnote VM to the format expected by the EGI site(s) (It is currently in VMWare format)
- Set up the Peachnote VM service on the sites
- Document feedback and requirements for the EGI Federated Cloud Task Force
Use case 2: the ability to run a small Hadoop and HBase cluster in the cloud. Being able to spin a HBase cluster using Apache Whirr on the EGI cloud infrastructure would be perfect, but a custom deployment would be a great first step.
Additional Files
- Peachnote use case overview slide from the HelixNebula workshop of the EGI Technical Forum (Slide 3): https://indico.egi.eu/indico/getFile.py/access?contribId=202&sessionId=84&resId=0&materialId=slides&confId=1019