- This line was added.
- This line was removed.
- Formatting was changed.
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.
As a service owner, I need a fully configurable VM which let us deploy our service interface
As a service owner, I want to be able to deploy the service in an automated way using the Cloud
|As a researcher, I would be interested in using GPUs.|
|As a researcher, I need the permanent computational capacity to run analyses regularly on my database.|
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.
Description of action
Dependency on 3rd party services (EOSC-hub or other)
OBM system is deployed in the Cloud as a long-running service
EGI Cloud Compute service
OBM Computational Node is deployed in the Cloud as a long-running service
|EGI Cloud Compute service, OpenBioMaps|
- Requirement number: Use numbers RQ1, RQ2, RQ3, ...
|Link to Requirement JIRA ticket|
Source Use Case
EOSC-hub to provide an FTS data transfer service
OpenBioMaps deployment in the EGI Cloud Compute service
|OpenBioMaps Computational Node deployment in the EGI Cloud Compute service||done||UC2|
Amount of requested resources
|EGI Cloud Compute||1 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 Storage||1 x 2TB||Until end of EAP (end of 2020 as of now)|
|Infrastructure Manager||Orchestrate deployment||Until end of EAP (end of 2020 as of now)|
|Table of Contents|