| 목차 |
|---|
| 페이지 속성 | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
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. |
Technologies considered and assessed from EOSC-hub
....
....
Requirements towards EOSC-hub developers and providers
Technical Requirements
Requirement number | Requirement title | Link to Requirement JIRA ticket | Source Use Case | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
RQ1 | EOSC-hub to provide an FTS data transfer service |
| UC1, 2, 3 | ||||||||
RQ2 | EOSC-hub to provide Kubernetes as a service |
| UC1, 4, 5 |
...
- X concurrent users
- Y container throughput / month
- Simultaneous staging of containers to Z sites
Assessment plan
FTS
.....
Kubernetes
....