Copernicus Data in the EGI infrastructure Diego Scardaci Senior User Community Support and Outreach officer

Aims of the pilot Provide access to the Copernicus Data within the EGI infrastructure Mechanisms to automatically download data for a given area in a certain time window Validate the access through standard EO interfaces (e.g. DHUS) Local and remote access Validate the access through the EGI Data Hub (OneData) Compare the performance

Partners involved Terradue CESNET Cyfronet EGI.eu Geohazard and Hydrology TEPs service provider Service provider for other EO exploitation platforms CESNET EGI FedCloud Service Provider Collaborative Ground segment node for the Czech Repubblic Cyfronet EGI DataHub service provider OneData technology provider EGI.eu Coordination and technical support

Test cases Access Copernicus Data from VMs running in EGI FedCloud: VMs and data in the same provider and data access via DHUS interface VMs and data in the same provider and data access via the EGI DataHub VMs and data in the different providers and data access via DHUS interface VMs and data in the different providers and data access via the EGI DataHub

Use case VITO Sentinel’s Biopar application embedded in the ESA Geohazard Exploitation platform (GEP) Copernicus data from Belgium and Mali Time window of 1 month (most recent data) Cloud resources Master node: 2 CPUs, 8 GB RAM, 100 GB disk N Slave nodes: 2 CPUs, 8 GB RAM, 200 GB disk GEP is already using EGI FedCloud resources for its production operation

Actions and Roles CESNET Make Copernicus data of Belgium and Mali available (1 month time window) DHUS EGI DataHub (OneData provider registered in the DataHub) Provide Cloud resources to Terradue to run the VMs (FedCloud or Geohazard VO ?)

Actions and Roles Terradue: Configure/Modify the SW to access data from EGI HTTP and POSIX ? Deploy VMs @ CESNET Deploy VMs @ 2nd FedCloud provider Run the pilot Collect performance measurements

Actions and Roles CYFRONET EGI.eu Support CESNET on the deployment and configuration of the OneProvider instance EGI.eu Coordinate the pilot activity Look for the second provider

Pilot expected outcomes Validate the usage of the EGI DataHub for a real use case Performance comparison between the DataHub and DHUS interfaces to access EO data Performance measurements in case of remote access to data within the EGI Federation Possible future collaboration with GEANT Exploit the pilot outcomes in NextGEOSS and others EO cases

Timeline To be discussed today