...
Step | Description of action | Dependency on 3rd party services (EOSC-hub or other) | |
|---|---|---|---|
UC1 | The DODAS admin requests the automated deployment of a DODAS cluster | TOSCA template to be submitted to the PaaS Orchestrator | |
UC2 | The DODAS admin checks the status of the DODAS core services | Needs integration with some monitoring service. Is there anything already available in EOSC-HUB? | ...hub? |
UC3 | Users access remote stored data from the DODAS cluster | Cluster configuration shall support OneData/XRootD integration. XRootD is maintained externally to EOSC-hub | |
| UC4 | Jobs running on DODAS clusters store temporary data on local cluster | ||
| UC5 | Jobs running on DODAS clusters access software |
Requirements
Technical Requirements
...
Requirement ID | EOSC-hub service | GAP (Yes/No) + description | Requirement description | Source Use Case |
|---|---|---|---|---|
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/XRootXRootD | 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 |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|