페이지 트리

버전 비교

  • 이 줄이 추가되었습니다.
  • 이 줄이 삭제되었습니다.
  • 서식이 변경되었습니다.

...

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):

  1. AAI integration
  2. Connect cloud to the RDSDS
  3. Connect cloud to the reference application distribution service
  4. Policy compliance with policies (ELIXIR, EGI cloud, and EOSC-hub policies)

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)

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):

  1. ...use EOSC-hub FTS service...
  2. ...
Same as above.

UC3

Requesting the replication of a reference/core dataset to my local cloud (researcher perspective):

  1. ...use EOSC-hub FTS service...
  2. ...
Same as above.
UC4

Making reference/core applications available for replication to the federated cloud providers (data provider perspective):

  1. ...use EOSC-hub 'Kubernetes as a Service'...
Same as above.
UC5

Requesting the replication of a reference/core application to my local cloud (researcher perspective):

  1. ...use EOSC-hub 'Kubernetes as a Service'...
  2. ...
Same as above.



Requirements

Technical

...

Requirements → This table will be removed and the items will be recorded as JIRA tickets for traceability


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

...