...
Requirement ID | EOSC-hub service | GAP (Yes/No) + description | Requirement description | Source Use Case |
|---|---|---|---|---|
RQ1 | FTS data transfer service | Yes: EOSC-hub does not provide a centrally managed FTS service | ELIXIR would like to use a centrally provided FTS service as RDSDS. The FTS should provide isolation of the ELIXIR content from other communities' datasets. | UC1, 2, 3 |
RQ2 | Kubernetes as a service | Yes: EOSC-hub does not provide a centrally managed Kubernetes service that'd allow a community to orchestrate containers on EGI/EOSC IaaS clouds, and on community IaaS clouds (given that those clouds are compatible with the Kubernetes service) | EOSC-hub to provide a centrally managed Kubernetes service, which would allow ELIXIR to orchestrate containerised applications on the federated clouds. These clouds would be federated similarly, but not necessarily identically to the EGI Federated Cloud. (The protocols, interfaces and policies to use in the ELIXIR federation is still under definition.) | UC1, 4, 5 |
| RQ3 | Application distribution service | Partial: EOSC-hub provides a centrally application distribution service with AppDB but it's currently focused on VM images (Virtual Appliances), ELIXIR may need to distribute applications on docker containers or as code repositories (e.g. ansible playbooks to configure VMs) | EOSC-hub to provide a centrally provided application distribution service so applications can be easily executed on any of the federated clouds supporting ELIXIR | UC1, 4 |
Capacity Requirements
The cloud capacity will initially come from the ELIXIR CC members (EBI, CESNET, CSC). Others will join in a second stage.
...