Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @

Difference between revisions of "Template:FedCloudUseCases"

From EGIWiki
Jump to navigation Jump to search
Line 37: Line 37:
* File 2
* File 2
{{{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):

Revision as of 16:44, 9 October 2012

General Information

  • Status: planned, active, completed
  • Start Date: DD/MM/YY
  • End Date: DD/MM/YY
  • contact:
  • External contact: contact@something

Short Description

Short description of the FedCloud Use Case.


Use case 1

Short intro can be provided here ...

  1. Task 1
  2. Task 2
  3. ...
Use case 2

Short intro can be provided here ...

  1. Task 1
  2. Task 2
  3. ...

Additional Files

  • File 1
  • File 2