The EOSC-hub project has ended. This space is READ ONLY

Short description

This EAP case would like to create a service with EOSC that allows multiple users to run tasks that are above the level of a PC through the same interface. In fact, it would like to develop a “service in service” - specifically for projects that collect nature conservation and biodiversity data.

To serve these diverse tasks this case needs a fully configurable VM which let us deploy OpenBioMaps service interface (API) which will be available in the OpenBioMaps Network and provide computation capacity access to the involved projects.

Type of communityOthers (EAP) 
Community contactDr. Miklós Bán (banm@vocs.unideb.hu)
InterviewerMiguel Caballer
Date of interview
Meetings
Supporters

User stories


We would like to create a service with EOSC that allows multiple users to run tasks that are above the level of a PC through the same interface. In fact, we would like to develop a “service in service” - specifically for projects that collect nature conservation and biodiversity data.

To serve these diverse tasks we need a fully configurable VM which let us deploy our service interface (API) which will be available in the OpenBioMaps Network and provide computation capacity access to the involved projects.

According to our recent experiences in our PC based local computational cluster, the number of processors is the most important in these ecological analyzes. A “typical” analysis is now running at an acceptable rate on 16 threads. The parallel computing requirements of image analysis can be much higher, and GPU usage can be interesting there. Some analyzes, for example, genetic analyzes or larger spatial analyzes require a lot of memory.


No.

User stories

US1

As a service owner, I need a fully configurable VM which let us deploy our service interface

US2

As a service owner, I want to be able to deploy the service in an automated way using the Cloud

US3

As a researcher, I would be interested in using GPUs.

US4

As a researcher, I need the permanent computational capacity to run analyses regularly on my database.


Use cases

Instruction

The OpenBiomaps system is deployed as a single VM on EGI Cloud Compute. Services are launched using docker compose. 

The OpenBioMaps Computational Service deployed on a VM on EGI Cloud Compute. This service API is available for remote database-based compuation servive for all OpenBioMaps servers and for the all OpenBioMaps users.

Technical Plan:

https://drive.google.com/file/d/1t4JA53-GmY2_nc4dfFSU6iPEfr7bsHAm/view?usp=sharing


Step

Description of action

Dependency on 3rd party services (EOSC-hub or other)

UC1

OBM system is deployed  in the Cloud as a long-running service

EGI Cloud Compute service

UC2

OBM Computational Node is deployed  in the Cloud as a long-running service

EGI Cloud Compute service, OpenBioMaps

...





Requirements

Technical Requirements


Instruction

- Requirement number: Use numbers RQ1, RQ2, RQ3, ...
- Requirement title: Use a short but descriptive title. Use the same title in the Jira ticket 'Summary' field
- Link to requirement JIRA ticket: Open a ticket in <this JIRA queue  https://jira.eosc-hub.eu/projects/EOSCWP10/issues/EOSCWP10-4?filter=allopenissues> (click on 'CREATE' button in the middle-top of JIRA)
- Source use case: Refer back to the use cases above (UC1, 2, ...)



Requirement number

Requirement title

Link to Requirement JIRA ticket

Source Use Case

Example

EOSC-hub to provide an FTS data transfer service

EOSCWP10-21 - Getting issue details... STATUS

UC1

RQ1

OpenBioMaps deployment in the EGI Cloud Compute service

doneUC1

RQ2

OpenBioMaps Computational Node deployment in the EGI Cloud Compute servicedoneUC2





Capacity Requirements


EOSC-hub services

Amount of requested resources

Time period

EGI Cloud Compute1 VM instances linux based:
48 CPU per VM,
96GB RAM per VM,
20 GB disk per VM,
Ports open: 22, 80, 443, 5432, 9880
Until end of EAP (end of 2020 as of now)
EGI Object Storage1 x 2TBUntil end of EAP (end of 2020 as of now)
Infrastructure ManagerOrchestrate deploymentUntil end of EAP (end of 2020 as of now)