...
The following table provides a mapping of components in the RACC architecture to EOSC provided services:
Component | EOSC Service | Description |
|---|---|---|
Federated Access | EGI Check-In, using COmanage for collaboration management. | COmanage is the federated collaboration management system of choice. A pilot is underway to federate using EGI Check-In. Depending on outcome, alternative federation providers (notable Geant or SURFnet) may be considered. |
Container Based Processing | EGI/Grid and High Throughput processing clusters | It is envisioned that the processing systems support CWL based workflows using Singularity containerized applications. RACC would be interested in a workflow management service provided by EOSC for this type of processing capability. Alternatively, a workflow management service would need to be deployed and maintained as an RACC specific service. |
Application Distribution | CVMFS | The main objective is to provide transparent local access to selected application containers and software installations on processing clusters. |
User Workspace | dCache WEBDAV & Macaroons | The user workspace is envisioned to use the same storage infrastructure as the instrument data archive. The objective is to move away from personal X509 based access over GridFTP toward Macaroon based access over WEBDAV. |
Science Data Repository | B2SHARE, EPIC/B2HANDLE, B2FIND | User generated science-level data is to be entered in B2SHARE. Optionally, data in the LOFAR instrument data archive will be registered in B2FIND. A LOFAR-scoped handle generating service is to be provided by EPIC/B2HANLDE. |
Requirements for EOSC-hub
...