...
| 페이지 속성 | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Ambition
The CC drives collaboration between EOSC-hub and the ORFEUS-EIDA federation of EPOS. The CC collects and assesses the requirements of the solid-Earth science community, with a specific focus on Seismology, and addresses them by leveraging the EOSC-hub technical offerings. The CC delivers a software platform that facilitates access and exploitation of computational resources; it supports and fosters harmonisation of best practices for data management at ORFEUS-EIDA; and it enables the generation of seismological products customised on user requirements. By the end of the EOSC-hub project the CC aims to have a pre-production quality, modular software platform that could be deployed at (selected) data centres. However, the actual deployments will depend on agreements for service provisioning and operation.
...
Architecture & EOSC-hub technologies considered/assessed
...
Requirements for EOSC-hub
...
Requirement number | Requirement title | Link to Requirement JIRA ticket | Source Use Case | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Example | EOSC-hub to provide an FTS data transfer service |
| UC1 | ||||||||||
RQ1 | iRODS instance accessible from the Jupyter environment and federated with local B2SAFE/iRODS instances
| UC2, UC3 | |||||||||||
RQ2 | Customisable and permanent kernels in Jupyter (EGI Notebook)
| UC3 | |||||||||||
| RQ3 | Personal data folder with staged data available for mounting in the Jupyter notebook
| UC3 | |||||||||||
| RQ4 | Operating SeedLink slarchive and rsync for data acquisition, while ArcLink and FDSNWS for data exposal. WFCatalog for quality metrics collection and distribution, as well as B2SAFE for data replication and Webreqlog for statistics sum-ups | UC4 | |||||||||||
| RQ5 | Execution of distributed Jupyter notebooks | UC5 | |||||||||||
| RQ6 | A centralised catalogue of policies. It should collect descriptions of data management policies and make them available (via API and metadata) | UC4 |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|
| EGI Notebooks service | Ideally we need this service deployed at the providers hosting our replicated archives i.e. SURFsara, KIT, CINECA and GRNET. It should be coupled with a scratch space where data from the archive can be staged to be processed and results temporarily stored. Size ~1TB | Duration of the project |
| B2SAFE | It is already in place and running at the 4 nodes. The requirements vary from site to site and there are local agreements. | It should be sustained after the project ends |
| B2ACCESS | It should be sustained after the project ends | |
Validation plan
The AAI based on B2ACCESS was validated in a test case targeting the AlpArray community. Future validation will include the whole EIDA user community.
The integration of the staging and pocessing services will be validated via pilots targeting selected EIDA users. The extent of the pilots depends quite substantially on the resources available...
The execution and management of the policies will be validated at the 4 data centres: KNMI, GFZ, NOA and INGV. Results will be presented to the remaining EIDA partners