...
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 and made collect descriptions of data management policies and make them available (via API and metadata) descriptions of data management policies | 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 | |
...