"The first half of the project resulted in the launch of the first platform and testbed prototype (codenamed DEEP-Genesis). After this initial prototipe was launched, an extensive testing phase was performed, together with use cases broth within the project as well as external communities, in order to assess and validate the platform functionality. This has led to the 2nd project release, producing the DEEP-Rosetta platform. DEEP-Rosetta is composed of three different services, as depicted in the attached diagram, resulting in the service offer included in the DEEP-HybridDataCloud service catalog towards the EOSC. These services can be used jointly as a whole framework, or individually and are the following:
• The DEEP training facility (
https://train.deep-hybrid-datacloud.eu/(öffnet in neuem Fenster)) as the service providing access to resources leveraging accelerators for intensive computing, exploiting the PaaS cloud layer or HPC resources.
• The DEEP as a Service (
https://deepaas.deep-hybrid-datacloud.eu/(öffnet in neuem Fenster)) , which provides an easy and automated way to deploy existing applications in the catalog as services.
• The DEEP Open catalog (
https://marketplace.deep-hybrid-datacloud.eu/(öffnet in neuem Fenster)) a marketplace where users can browse, retrieve, share and store their applications.
• The data and storage services, where user data and results can be stored that are external to the project, but integrated with us.
These services are being deployed on resource providers that are part of production pan-European e-Infrastructures. In this regard we have ensured that the deployed services are in line with the operational requirements that are enforced at the e-Infrastructure level. Besides, we have linked with industry stakeholders through the EOSC Digital Innovation Hub (DIH).
Extensive work has been performed in all the software quality and maintenance related activities, involving both software developers and users since the initial phases. This co-design methodology was carried out in order to obtain a high degree of acceptance on the software related procedures, avoiding excessive burden on software development teams. Moreover, these activities are being done in coordination with other projects, as reflected in the publication of ""A set of common software quality assurance baseline criteria for research projects"" document (
http://hdl.handle.net/10261/160086(öffnet in neuem Fenster)). Besides, we have ensure that the developed services follow the existing recommendations to be integrated into the EOSC realm."