...
Requirement ID | EOSC-hub service | GAP (Yes/No) + description | Requirement description | Source Use Case | Link to JIRA Ticket | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Example | EOSC-hub AAI | Yes: EOSC-hub AAI doesn’t support the Marine IdP | EOSC-hub AAI should accept Marine IDs | UC1 | |||||||||
RQ1 | INDIGO PaaS | No | Automated deployment of the DODAS cluster on top of heterogeneous cloud environments through TOSCA orchestration | UC1 | |||||||||
RQ2 | ? | Yes: check if EOSC-hub provides a monitoring service for collecting monitoring data | Monitoring information gathering | UC2 |
| ||||||||
| RQ3 | OneData/XRootD | No | User data remote access | UC3 | |||||||||
| RQ4 | OneData/XRootD | No | Store temporary data locally | UC4 | |||||||||
| RQ5 | CVMFS (client and stratum 0) | No | Usage of specific global file system for software distribution | UC5 | |||||||||
| RQ6 | OneData | No | Job input and output sandbox data movement | UC6 | |||||||||
| RQ7 | INDIGO-IAM | No | Provide authN/authZ for DODAS users | UC7 | |||||||||
| RQ8 | ESACO, AAI EOSC-hub?? | ESACO is being successfully used by the providers of the enabling facility | Resource providers integration with INDIGO-IAM | UC8 |
| ||||||||
| RQ9 | APEL? | Yes: how to extract accounting data from heterogeneous providers (including public clouds) | Accounting data gathering | UC9 |
|
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|