...
Requirement ID | EOSC-hub service | GAP (Yes/No) + description | Requirement description | Source Use Case | Related tickets | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
RQ1 | B2STAGE | POTENTIAL: Need to check whether EGI DARIAH AAI POTENTIAL: Can B2STAGE be made to transfer files between | Analyzed and will not be integrated | ||||||||||
RQ2 | B2SHARE | No | Integrate with DARIAH Gateway | UC2 | Analyzed and will not be integrate | ||||||||
| RQ3 | B2DROP | No | Integrate with DARIAH Gateway | ||||||||||
| RQ4 | B2ACCESS | UNKNOWN | Integrate DARIAH Gateway AAI (not sure this is really needed long term since hopefully it won't matter which EOSC AAI mechanism is used) | Analyzed and will not be integrate. EGI AAI is used instead. | |||||||||
| RQ5 | B2FIND | NO: Existing DARIAH metadata already harvested | Make data discoeverable through metadata searches | Analyzed and will not be integrated. | |||||||||
| RQ6 | B2SAFE | POTENTIAL: May need to allow havestable metadata from B2SAFE instances | Integrate with DARIAH Gateway | Analyzed and will not be integrated. | |||||||||
| RQ7 | PaaS Orchestrator | UNKNOWN - Plan is to integrate with WS-Pgrade YES: Need to define whether this will be a deployable software compt or use a central instance. | DARIAH Gateway is not a deployable software. A central instance is used. Invenio-as-a-Service is | Analyzed and will not be integrated for DARIAH Gateway Integrated with Invenio-as-a-Service | |||||||||
| RQ8 | EGI FedCloud/ FedCloud Containers/ Nove-docker/OneDock | YES: Can users run arbitrary containers on fedcloud resources/ can DARIAH user containers be made available for general usage | Extend the gateway functionality to support creating |
Completed | |||||||||
| RQ9 | FutureGateway | UNKNOWN | The science gateway will internally deploy a copy of |
Completed | |||||||||
| RQ10 | B2FIND/B2SHARE | UNKNOWN: Can Semantic Search Engine. harvest from B2FIND NO - B2SHARE can already be harvested | Make data stored in EUDAT repositories findable through the Semantic Search Engine. | Analyzed and will not be integrated. | |||||||||
| RQ11 | EGI FedCloud/ | NO | The VLE will be integrated with the EGI compute and storage resource infrastructure and integrated as a new user-oriented service of the EGI DARIAH CC Gateway. The current client- server model will ported to the EGI FedCloud infrastructure, while the underlying data management will be integrated with the INDIGO OneData solution and EUDAT B2Share and B2Stage service to transfer data to EGI FedCloud for batched processing of editing procedures. | VLE is not part of the DARIAH T. Analyzed and will not be integrated. |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|
| OneData | 50TB | EOSC-Hub project lifetime + 2 years |
| EGI FedCloud | 300 cores/2TB memory (total) | EOSC-Hub project lifetime + 2 years |
| B2DROP | ||
| B2SHARE | ||
| B2FIND |