...
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 and orchestration service (a new requirement to EOSC-hub) ELIXIR cloud federation policies, protocols and interfaces. (under definition) |
UC2 | Making reference/core datasets available for replication to the federated cloud providers (data provider perspective):
| Same as above. |
UC3 | Requesting the replication of a reference/core dataset to my local cloud (researcher perspective):
| Same as above. |
| UC4 | Making virtualised, reference/core applications available for replication and orchestration on the federated cloud providers (data provider perspective):
| Same as above. |
| UC5 | Requesting the replication of a reference/core application to my local cloud (researcher perspective):
| Same as above. |
Requirements
Technical
...
Requirement ID
...
Requirements
Requirement number | Requirement title | Link to Requirement JIRA ticket | GAP (Yes/No) + description | Requirement description | Source Use Case | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
RQ1 | EOSC-hub to provide an 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 and orchestration service so centrally applications can be easily instantiated on any of the federated clouds that support ELIXIR. | UC1, 4 |
...