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 @ egi.eu.
Difference between revisions of "FedCloudPeachnote"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
Building up the corpora of musical sheets requires significant amount of computing capacity. Millions of sheets need to be converted from JPG images to music XML, sometimes multiple times, using different configurations of the converter algorightm. Peachnote is already integrated with the Simple Queue Service (SQS) of Amazon. Amazon SQS will remain the coordinator of computation, with site(s) of the EGI Federated Cloud used for the calculations. | Building up the corpora of musical sheets requires significant amount of computing capacity. Millions of sheets need to be converted from JPG images to music XML, sometimes multiple times, using different configurations of the converter algorightm. Peachnote is already integrated with the Simple Queue Service (SQS) of Amazon. Amazon SQS will remain the coordinator of computation, with site(s) of the EGI Federated Cloud used for the calculations. | ||
http://www.peachnote.com | http://www.peachnote.com | | ||
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. | | |||
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 | |||
}} | }} | ||
Revision as of 14:51, 9 October 2012
General Information
- Status: active
- Start Date: 11/09/2012
- End Date:
- EGI.eu contact: Gergely Sipos / gergely.sipos@egi.eu
- External contact: Vladimir Viro / vladimir@viro.name
Short Description
Short description of the FedCloud Use Case.
Use Case
Specific description of the Use Cases
Additional Files
- File 1
- File 2