...
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 | EOSC-hub AAI | No | Authenticate users to the portal using OpenID Connect | |
RQ2 | Cloud Compute | No | Create VMs for hosting the portal database | |
| RQ3 | Cloud Container Compute | Unclear: Managed Kubernetes offered as alternative platform to AWS ECS, still requires deeper evaluation from the TS to understand if there are gaps | Current solution running on AWS ECS, need an alternative solution on EOSC-hub that can provide the same functionality. | |
| RQ4 | Cloud Compute/Cloud Container Compute | Yes: EC3 able to spawn scalable Hadoop as needed, still missing HBase. Not packaged as a service currently | Need for a Hadoop/HBase as a Service that is able to scale with demand | |
| RQ5 | Cloud Container Compute/EGI HTC | Yes: although similar functionality can be achieved with open source components on top of the existing services, the architecture of the application will need to be adapted. Further evaluation of the services from the TS developers is required to understand additional gaps | Provide a similar service to AWS Beanstalk for running job-like applications with containers that are triggered with messages sent via AWS SQS | |
| RQ6 | Cloud Compute/Cloud Container Compute | Yes: no function as a service is provided in the EOSC-hub | Use of AWS Lambda (python, java, and js) for lightweight computation and triggered via events |
Requirement number | Requirement title | Link to Requirement JIRA ticket | Source Use Case | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Example | EOSC-hub to provide an FTS data transfer service |
| UC1 | ||||||||
RQ1 |
Capacity Requirements
EOSC-hub services | Amount of requested resources | Time period |
|---|---|---|