...
Requirement ID | EOSC-hub service | GAP (Yes/No) + description | Requirement description | Source Use Case | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Example | RQ1 | EGI Check-in | No | eduGAIN support for EOSC-hub AAI | ||||||||||
RQ2 | OPENCoastS | Yes: OPENCoastS does not manage authorization policies | Attribute provision for OPENCoastS | |||||||||||
| RQ3 | OPENCoastS | No | Broadcast simulation composition | |||||||||||
| RQ4 | WaTTS | No | OpenID Connect token translation to x509 certificate for Grid submission | |||||||||||
| RQ5 | DIRAC4EGI | No | Multi-site job submission | |||||||||||
| RQ6 | <NOT_AVAILABLE> | Yes: | EOSC-hub AAI doesn’t support the Marine IdPEOSC-hub AAI should accept Marine IDs | UC1 | RQ1 | <Gap service> | Yes: …. | RQ2 | Cloud Compute | No | Create VMs ia a gateway | UC2udocker should be the service to be used but it is not currently in the EOSC-hub service catalogue | User-space Docker container execution | |
| RQ7 | DIRAC4EGI | No? | Job output management | |||||||||||
| RQ8 | EGI DataHub B2STAGE B2SAFE | No? | OPENCoastS need to store high-quality/premium forecast archives in permanent storage | |||||||||||
| RQ9 | EGI DataHub B2FIND B2NOTE | No? | OPENCoastS need to handle metadata for user access to historical data | |||||||||||
| RQ10 | B2HANDLE B2DROP B2SHARE | No? | OPENCoastS need to expose historial catalogue as Open Data | |||||||||||
| RQ11 | <NOT_AVAILABLE> | Yes: EOSC-hub does not provide Ansible consulting | Automated deployment using Ansible of OPENCoastS service | |||||||||||
| RQ12 | PaaS Orchestrator | Yes: TOSCA templates need to be provided | OPENCoastS service deployment in the Cloud | |||||||||||
| RQ13 | ARGO | Yes: ARGO does not currently support MaaS delivery | Monitoring as a service | |||||||||||
| RQ14 | Accounting | Yes: Cloud storage accounting not supported | Tracking compute and storage consumption |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|