...
Step | Description of action | Dependency on 3rd party services (EOSC-hub or other) | ||
|---|---|---|---|---|
UC1 | User logs in the OPENCoastS service using eduGAIN | EGI Check-in | ||
UC2 | ... | ... | OPENCoastS service manages the authorization/attribute provision | OPENCoastS platform |
UC3 | OPENCoastS service obtains a x509 certificate for Grid submission | WaTTS | ||
| UC4 | User constructs a broadcast simulation | OPENCoastS platform | ||
| UC5 | User submits jobs with the broadcast simulation | DIRAC4EGI | ||
| UC6 | OPENCoastS service may support docker container execution | udocker | ||
| UC7 | User obtains outputs from the simulation for the next (at most) 72h | DIRAC4EGI | ||
| UC8 | OPENCoastS service automatically performs quality checks to identify high-quality/premium forecasts | OPENCoastS platform | ||
| UC9 | OPENCoastS service stores high-quality/premium forecasts | Data preservation service EGI DataHub | ||
| UC10 | User searches the catalogue of high-quality/premium forecasts for re-analysis | Data discovery Metadata and provenance service | ||
| UC11 | OPENCoastS service is deployed automatically | Ansible | ||
| UC12 | OPENCoastS service is deployed in the Cloud as a long-running service | PaaS orchestrator | ||
| UC13 | OPENCoastS service is monitored | ARGO | ||
| UC14 | User resource consumption (compute, data) is tracked and accessible | Accounting |
Requirements
Technical Requirements
...