Search

This document provides the final report on the services created in the C-SCALE project aimed to streamline data coming from Copernicus platforms and EOSC e-infrastructure compute providers. The report includes a description of the key exploitable results and the main services created during C-SCALE to ensure their exploitation, uptake and sustainability beyond the life of the project.

The C-SCALE Compute Federation delivers access to cloud and HPC/HTC resources to support Copernicus and Earth Observation related research activities. This document describes the services supported by the C-SCALE Compute Federation and how they support Copernicus and EO data analytics.

This document provides an updated report on the data types that are collected and generated per Work Package (WP), whether they will be shared with the public and how, whether they can be reused and how, and how they will be preserved during and after the end of the project. The first version of the Data Management Plan, submitted in March 2022 to the EC, included the information on the aforementioned topics until March 2022, while in this second and last version, in addition to the above, information on the data that the onboarded use cases collected and generated is provided as well as on the Intellectual Property Rights (IPR) of C-SCALE data is included.

This report presents an update of the assessment of the C-SCALE services provided through the Virtual Access (VA) mechanism to the users. These include computing and storage resources. The deliverable describes the existing VA installations, their management within the project, updates the usage metrics delivered from the start of the project (January 2021) until Month 24 (December 2022) and reports on the Green Computing metrics and initiatives from the C-SCALE providers.

This report presents an update of the assessment of the C-SCALE services provided through the Virtual Access (VA) mechanism to the users. These include computing and storage resources. The deliverable describes the existing VA installations, their management within the project, updates the usage metrics delivered from the start of the project (January 2021) until Month 18 (June 2022) and reports on the Green Computing metrics and initiatives from the C-SCALE providers.

This document provides a report on the data types that are collected and generated per Work Package (WP), whether they will be shared with the public and how, whether they can be reused and how, and how they will be preserved during and after the end of the project. In this first version, the Data Management Plan is created based on the knowledge that the project members have so far, while a second – full – version will follow in the second half of the project.

This document will provide an initial report on the procedure that other Copernicus platform and EOSC e-infrastructure providers will have to follow to join the C-SCALE federation and description of engagement activities, key results and future plans beyond the life of the project.

This document will provide an initial report on the procedure that other Copernicus platform and EOSC e-infrastructure providers will have to follow to join the C-SCALE federation and description of engagement activities, key results and future plans beyond the life of the project.

International audience

The C-SCALE Compute Federation brings together European commercial (e.g. Copernicus DIAS) and public (from e-infrastructure) computing providers to deliver a federated infrastructure to support Copernicus and Earth Observation (EO) use cases that deal with data- and compute-intensive workloads. The federation makes computing e-Infrastructure, potentially consisting of multiple services provided collaboratively by several service providers, accessible through homogeneous interfaces using a common AAI framework. Hence, C-SCALE facilitates the deployment of research applications that make use of EO and Copernicus datasets, e.g. Sentinel-series satellite data, that are distributed across multiple providers. This document describes the overall architecture of the C-SCALE Compute Federation, that provides users with the baseline computing resources to perform Earth Observation related analytics on a distributed e-Infrastructure.

The C-SCALE Compute Federation brings together European commercial (e.g. Copernicus DIAS) and public (from e-infrastructure) computing providers to deliver a federated infrastructure to support Copernicus and Earth Observation (EO) use cases that deal with data- and compute-intensive workloads. The federation makes computing e-Infrastructure, potentially consisting of multiple services provided collaboratively by several service providers, accessible through homogeneous interfaces using a common AAI framework. Hence, C-SCALE facilitates the deployment of research applications that make use of EO and Copernicus datasets, e.g. Sentinel-series satellite data, that are distributed across multiple providers. This document describes the overall architecture of the C-SCALE Compute Federation, that provides users with the baseline computing resources to perform Earth Observation related analytics on a distributed e-Infrastructure.

The main purpose of this deliverable is to present the sustainability approach of the AGINFRA+ project results. Its target audience comprises representatives of external interested communities as well as the European Commission (i.e. main funder of the AGINFRA+ project). More precisely, the document examines three action lines, each dedicated to sustain a main output of the AGINFRA+ project, namely: Consultancy service to deploy and configure custom VREs for agri-food research communities: corresponds to Virtual Research Environments (VREs) that can be developed and deployed as a service to various agri-food communities based on (a) the D4Science infrastructure (https://www.d4science.org/) and (b) the customization of generic or domain specific services offered by various partners, which have been tested and validated with agri-food researchers during the project lifetime. Data Journals: corresponds to the two data journals that we have been set-up based on the ARPHA publishing platform (http://arphahub.com/), namely the Food Modelling Journal (https://fmj.pensoft.net/) and the Viticulture Data Journal (https://vdj.pensoft.net/) Thematic VREs: corresponds to the four VREs that have been set-up during the project lifetime for supporting the three user communities of the project, namely (a) one VRE for Agro-Climatic and Economic Modelling community, (b) two VREs for the Food Safety Risk Assessment Community and (c) one VRE for Food Security Community Additionally, the report examines the management of AGINFRA+ after the end of the project funding. More specifically, although in the project DoA it has been proposed the establishment of a legal entity form (through a not-for-profit association) for the further operation and evolution of AGINFRA+ as a joint venture of involved stakeholders, it seems that this solution will not be operational considering the blend of the consortium partners involved. Thus, it has been considered among the partners that it will be better cost and operational wise to manage AGINFRA+ through a Memorandum of Agreement for a specified period (e.g. until December 2020) that will ensure that AGINFRA+ will be active in the EU infrastructures map and available to users with the support needed. Finally, the report concludes with the presentation of the foreseen next steps and the decisions that need to be further discussed among the consortium partners during the last year of the project towards finalizing the proposed sustainability plan of the project results.

Three technology demonstrators developed withing BBMRI Competence Centre in EGI-Engage: • proteomic workflows deployed by BBMRI.cz, • complex genomic workflows deployed by BBMRI-NL, • BiobankCloud-based workflows deployed by BBMRI.se/KTH. All of the tools have been made available open source and the workflows have been validated not only on EGI.eu infrastructure, but also inside the private clouds of the biobanks to allow for processing of very sensitive personal data.

mpi-start is a set of scripts to close the gap between the workload management system of a Grid insfrastructure and the configuration of the nodes on which MPI applications are run. The package is used to help the user to start MPI applications on heterogeneous Grid sites. mpi-start provides an abstraction layer that offers a unique interface to start parallel jobs with different execution environments implementations. It supports several different MPI implementations under different batch systems. mpi-start was originally developed in the frame of the int.eu.grid project for the execution of MPI applications with the CrossBroker metascheduler and then extended its use as the official way of starting MPI jobs within EGEE. Currently, it is part of the EMI project. There is a trac page at http://devel.ifca.es/mpi-start with information about the development of mpi-start., This work is co-funded by the EC EMI project under the FP7 Collaborative Projects Grant Agreement Nr. INFSO-RI-261611.

El siguiente TFG se basa en el desarrollo de un programa en Java que modifique paquetes SIP (Session Initiation Protocol) que contengan solicitudes INVITE con el fin de mejorar las comunicaciones multimedia, sobre todo las videoconferencias. Esta modificación consistirá en seleccionar los codecs adecuados en función del ancho de banda disponible en la red de acceso del usuario. El trabajo está dirigido para su instalación en una Whitebox de Samknows, enmarcándose dentro del proyecto que la empresa está desarrollando junto con la Comisión Europea. La solución propuesta se desarrollará en tres partes: 1. Recepción del paquete: se desviará el paquete hacia un puerto determinado, donde nuestro programa tendrá una pila escuchando las solicitudes que lleguen y su tipo. 2. Obtención de la información multimedia: obtendremos la información multimedia de la carga SDP (Session Description Protocol) y la compararemos con la que nos daría una buena calidad en función del ancho de banda disponible en ese momento, quedándonos con los codecs comunes a ambos. 3. Modificación del mensaje: una vez sepamos los codecs comunes, modificaremos la carga SDP y posteriormente el mensaje, para enviarlo modificado al servidor. Esta modificación se realiza de manera transparente al usuario y en tiempo real, con el fin de obtener un mejor rendimiento y experiencia de usuario en las comunicaciones multimedia, sin que esto suponga una penalización en términos de instalación del software, utilización de éste y tiempo de espera para iniciar las comunicaciones. The next Bachelor Thesis is based on the development of a Java program that modifies SIP (Session Initiation Protocol) packets which contain INVITE request with the goal of improving multimedia communications, mainly videoconferences. This modification will consist on selecting the right codecs depending on the available bandwidth at the user access network. The job is focused for its installation in a Smaknows Whitebox, framing itself inside the project the company is developing with the European Commission (EC). The proposed solution will be developed in three steps: 1. Packet reception: the packet will be redirected towards a well-known port, where our program will have a stack which is listening to the arrived requests and its type. 2. Getting the multimedia information: we will get the multimedia information from the SDP (Session Description Protocol) load and we will compare it with the one that would give us good quality according to the available bandwidth at this moment, choosing the common codecs. 3. Message modification: when we know de common codecs, we will modify the SDP load and the message with it, and we will send de modified packet to the server. This modification is done transparently for the user and in real-time, with the purpose of getting a better performance and user experience in the multimedia communications, but don’t supposing a penalization in terms of software installation, use and wait time to start the communications Ingeniería de Sistemas Audiovisuales

The main purpose of this deliverable is to present the sustainability approach of the AGINFRA+ project results. Its target audience comprises representatives of external interested communities as well as the European Commission (i.e. main funder of the AGINFRA+ project). More precisely, the document examines three action lines, each dedicated to sustain a main output of the AGINFRA+ project, namely: Consultancy service to deploy and configure custom VREs for agri-food research communities: corresponds to Virtual Research Environments (VREs) that can be developed and deployed as a service to various agri-food communities based on (a) the D4Science infrastructure (https://www.d4science.org/) and (b) the customization of generic or domain specific services offered by various partners, which have been tested and validated with agri-food researchers during the project lifetime. Data Journals: corresponds to the two data journals that we have been set-up based on the ARPHA publishing platform (http://arphahub.com/), namely the Food Modelling Journal (https://fmj.pensoft.net/) and the Viticulture Data Journal (https://vdj.pensoft.net/) Thematic VREs: corresponds to the four VREs that have been set-up during the project lifetime for supporting the three user communities of the project, namely (a) one VRE for Agro-Climatic and Economic Modelling community, (b) two VREs for the Food Safety Risk Assessment Community and (c) one VRE for Food Security Community Additionally, the report examines the management of AGINFRA+ after the end of the project funding. More specifically, although in the project DoA it has been proposed the establishment of a legal entity form (through a not-for-profit association) for the further operation and evolution of AGINFRA+ as a joint venture of involved stakeholders, it seems that this solution will not be operational considering the blend of the consortium partners involved. Thus, it has been considered among the partners that it will be better cost and operational wise to manage AGINFRA+ through a Memorandum of Agreement for a specified period (e.g. until December 2020) that will ensure that AGINFRA+ will be active in the EU infrastructures map and available to users with the support needed. Finally, the report concludes with the presentation of the foreseen next steps and the decisions that need to be further discussed among the consortium partners during the last year of the project towards finalizing the proposed sustainability plan of the project results.