페이지 트리

버전 비교

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

...

No.

User stories

US1


ELIXIR wants to establish a federation of cloud sites, each providing storage and compute capacity for researchers. The federated clouds should be connected to a data replication service (Reference Data Set Distribution Service with the ELIXIR terminology - RDSDS) that enables ELIXIR to stage 'ELIXIR Core Data Resources' to the cloud sites on-demand. As a result, the cloud sites become data hosting nodes which are equipped with CPUs/GPUs and are suited for large-scale data analysis and analytics.

Centrally provided and curated datasets can ensure high quality research in any of the partner states/regions. Researchers can go to their 'local' ELIXIR cloud provider, choose an already pre-staged ELIXIR dataset or request the staging of an ELIXIR dataset, choose an application of their choice (from a VM catalogue or container catalogue), maybe upload some additional data and then perform data analysis/analytics.

Different conditions of access may apply at the different cloud sites, but it is expected that the cloud compute resources would be free at point of use for national/local researchers, while pay-for-use or other special conditions apply for foreigners.

The replication of community assets to national cloud providers maximises the utilisation of national funding and lowers the total cost of access for researchers. The services in the setup should recognise users via their community/national user accounts and user attributes. (i.e. integration with community and national AAI systems may be needed.)ELIXIR identity, therefore ELIXIR AAI should be integrated with the RDSDS as well as with the national clouds.

US2

The cloud federation can be also equipped with an ‘application replication and orchestration service’ that enables application providers to deploy community/reference applications to any of the federated cloud sites, and users to instantiate and use the applications on those sites.



...