페이지 트리

버전 비교

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

...

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

  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 virtualised, reference/core applications available for replication and orchestration on 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.


Architecture & EOSC-hub technologies considered/assessed

Policies and technologies to federate and share access to OpenStack clouds (build an ELIXIR cloud federation similar to the EGI Cloud service)

....

FTS file transfer service

....



Requirements for EOSC-hub providers

...