...
Requirements
Technical 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 | | Jira |
|---|
| server | EGI JIRA |
|---|
| serverId | 89b2a620-0cec-34da-8cfe-a343203be114 |
|---|
| key | EOSCWP10-21 |
|---|
|
| UC1, 2, 3 |
|---|
RQ2 |
|---|
Kubernetes as a service | Yes: does not 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, 4Kubernetes as a service | | Jira |
|---|
| server | EGI JIRA |
|---|
| serverId | 89b2a620-0cec-34da-8cfe-a343203be114 |
|---|
| key | EOSCWP10-22 |
|---|
|
| 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.
...