...
Step | Description of action | Dependency on 3rd party services (EOSC-hub or other) |
|---|---|---|
UC1 | Joining the cloud federation with a cloud site (cloud provider perspective):
| EOSC-hub centrally provided data distribution service (a new requirement to EOSC-hub!) EOSC-hub centrally provided application distribution service (a new requirement to EOSC-hub) |
UC2 | Making reference/core datasets available for replication to the federated cloud providers (data provider perspective):
| |
UC3 | Requesting the replication of a reference/core dataset for replication to my local cloud (researcher perspective):
| |
| UC4 | Making reference/core applications available for replication to the federated cloud providers (data provider perspective):
| |
| UC5 | Requesting the replication of a reference/core application to my local cloud (researcher perspective):
|
Requirements
Technical Requirements
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 |
|---|
Capacity Requirements
The cloud capacity will initially come from the ELIXIR CC members (EBI, CESNET, CSC). Others will join in a second stage.
Capacity requirements for the centrally provided EOSC-hub FTS:
- X concurrent users
- Y TB throughput / month
- Simultaneous staging of data to Z sites
Capacity requirements for the centrally provided Kubernetes as a service:
...
- X concurrent users
- Y container throughput / month
- Simultaneous staging of containers to Z sites