D8.1. Maitena Ilardia (Tecnalia). PIACERE brochure and public website. PIACERE Project (2021). 
Available online: https://zenodo.org/record/7057216#.YxiCm3ZBw2w
This deliverable is a key aspect in the outreach strategy as it services to create the PIACERE Brand.

D8.2. Leire Orue-Echevarria, Juncal Alonso (Tecnalia). PIACERE brochure and public website. PIACERE Project (2021).
Open access: https://zenodo.org/record/6821773#.YtZekXZBw2w
This deliverable aims at describing the initial Communication, Networking Plan and Dissemination Strategy of PIACERE project. The main objective of this strategy is to disseminate and outreach the project results

D2.1. Emmanuelle Morganti (HPE). PIACERE DevSecOps Framework Requirements specification, architecture and integration strategy – v1. PIACERE Project (2021).
Open access: https://zenodo.org/record/6801782#.Y0_GgnZBw2x
This deliverable will contain 1) all the functional, non-functional and technical requirements of the PIACERE DevSecOps Framework and of all the components to be developed in the context of the technical WPs (WP3, WP4, WP5 and WP6). This deliverable is tightly related to the corresponding use cases requirements deliverable in WP7 (D7.1). 2) the architecture of the DevSecOps framework [KR13] and the workflow, 3) the requirements of the DevOps infrastructure to be used in the development of PIACERE as well as the definition of the strategy and steps to be followed for the continuous integration of the PIACERE solution. This deliverable is the result of Task 2.1 and Task 2.3.

D3.1. Polimi. PIACERE Abstractions, DOML and DOML-E – v1. PIACERE Project (2021).
Open access: https://zenodo.org/record/6821651#.Y0_Gm3ZBw2x
This deliverable is the output of tasks 3.1, 3.2 and 3.3. It will contain the metamodel and the corresponding semantic and machine-readable descriptions of the aspects that are relevant to the main phases of the IaC lifecycle seamlessly integrated with the design and development of the IaC lifecycle. This metamodel will be then presented as an end-user language enabling the modelling of the different elements needed for the infrastructure provisioning, configuration management and deployment, the deployable infrastructural components, constraints and so on. The various iterations will seek and take into consideration the feedback from PIACERE’s end users and, possibly, other users outside the project to ensure that the language is sufficiently powerful and simple to use.

D3.4 Lorenzo Blasi (HPE). Infrastructural code generation – v1. PIACERE Project (2021).
Open access: https://zenodo.org/record/6821657#.Y0_Gr3ZBw2x
This deliverable will present the outcome of Task T3.4. Each deliverable will comprise both a software prototype [KR3] and a Technical Specification Report. The document will include the ICG technical design and will report related research results.

D3.7 Marc Gil, Alfonso de la Fuente, Ismael Torres (Prodevelop). PIACERE IDE – v1. PIACERE Project (2021).
Open access: https://zenodo.org/record/6821671#.Y0_GyHZBw2x
This deliverable is the output of Task 3.5 and it will also be iterative. The deliverable will be composed of a software prototype and a technical design document. This outcome will present the IDE resulting from the integration of KR1, KR3 - KR8. The software will be accompanied by a Technical Specification Report

D4.1 Michele Chiari, Michele De Pascalis, Matteo Pradella (Polimi). Infrastructural model and code verification – v1. PIACERE Project (2021).
Open access: https://zenodo.org/record/6821696#.Y0_G8XZBw2x
This deliverable describes the development of the model checking tool for IaC in the PIACERE project.
Two prototype model checkers are presented. The first one targets the TOSCA IaC specification language and has been developed as a proof-of-concept for evaluating different possible model-checking backends. The second one is targeted to the PIACERE DOML specification language in one of its current form, still at an early development stage. It will be further implemented by exploiting the insights learned from the first prototype. The work described in this deliverable contributes to KR4 from WP4.

D4.4 Matija Cankar (XLAB). IaC Code Security and components security Inspection - v1. PIACERE Project (2021).
Open access: https://zenodo.org/record/6821706#.Y0_HBXZBw2x
This deliverable will present the outcome of Task T4.2 and Task T4.3. The deliverable comprises both a
software prototype [KR6-KR7] and a Technical Specification Report. The document will include the Security Inspector technical design and implementation aspects. The document will also include the Security Inspector technical design and implementation aspects

D5.1 Josu Díaz de Arcaya (Tecnalia). IaC execution platform prototype – v1. PIACERE Project (2021).
Open access: https://zenodo.org/record/7310937#.Y20KDXbMI2x
The main outcomes of Task 5.1 - PIACERE IaC Execution Manager Prototype are presented in this deliverable. This deliverable corresponds to Key Result 10.

D5.4 Radosław Piliszek (7Bulls). Canary environment prototype – v1. PIACERE Project (2021).
Open access: https://zenodo.org/record/6821731#.Y0_HN3ZBw2x
The main outcomes of Task 5.2 - PIACERE Canary environment for IaC behaviour testing and simulation - are presented in this deliverable. This deliverable corresponds to Key Result 8 – Canary Sandbox Environment.

D5.7 Eneko Osaba (Tecnalia). IOP prototype – v1. PIACERE Project (2021).
Open access: https://zenodo.org/record/6821735#.Y0_HSXZBw2x
The main outcome of T5.3 from M1 to M30 will be presented in this deliverable. Each deliverable will have a Technical Specification Report and a software prototype [KR9], including the explanation of the algorithms

D6.1 Tecnalia. PIACERE run-time monitoring and self-learning, self-healing platform – v1. PIACERE Project (2021).
Open access: https://zenodo.org/record/6821765#.Y0_HXXZBw2x
This deliverable will contain the main outcomes from M1 to M30 of T6.1-T6.4 due to the high dependency of all the different tasks. It will include the monitoring stack coming from task 6.1 with all the time series data collected as well as the monitoring from the security policies from task 6.4, the set of machine learning algorithms (task 6.2) that comprise the self-learning mechanisms and the self-healing strategies (task 6.3) that trigger an optimized redeployment (see WP5). It will be an iterative process. Each deliverable will comprise a Technical Specification Report.

D2.3 Radosław Piliszek (7Bulls). PIACERE DevSecOps Framework – v1. PIACERE Project (2022).
Open access: https://zenodo.org/record/6821649#.Y0_HeXZBw2x
This deliverable will integrate all the components developed by the other technical WPs in the PIACERE DevSecOps Framework. Different versions of the PIACERE DevSecOps Framework will be provided following an incremental approach. The first version will be an initial prototype with the core functionalities implemented; the second version will augment these functionalities taking into consideration the feedback coming for the use cases and the final version will include corrections and feedback coming from the implementation of the use cases. The software will be accompanied by a Technical Specification Report. When appropriate, the architecture definition of the DevSecOps framework will be updated

D8.3 Leire Orue-Echevarria, Maitena Ilardia (Tecnalia), Galia Nedeltcheva (Polimi). Dissemination, communication and networking report - Report – v1. PIACERE Project (2022).
Open access: https://zenodo.org/record/6821779#.Y0_Hj3ZBw2x
This deliverable will explain the dissemination and communication activities followed during the reporting periods as well as the results from these activities and will update project’s dissemination and communication plan respectively. This report will also contain the relevant activities executed to foster a close collaboration with projects related to PIACERE, as well as future networking plans.

D2.2 PIACERE DevSecOps Framework Requirements specification, architecture and integration strategy - v2
Open access:

D2.7 PIACERE Abstractions, DOML and DOML-E - v2
Open access:

D3.5 Infrastructural code generation - v2 
Open access:

D4.2 Infrastructural model and code verification - v2
Open access:

D4.5 IaC Code Security and components security Inspection - v2 
Open access:

D5.2 IaC execution platform prototype - v2
Open access:

D5.5 Canary environment prototype - v2
Open access:

D5.8 IOP prototype - v2
Open access:

D6.2 PIACERE run-time monitoring and self-learning, self-healing platform - v2 
Open access:

D2.4 PIACERE DevSecOps Framework - v2
Open access:

D3.3 PIACERE Abstractions, DOML and DOML-E - v3
Open access:

D3.6 Infrastructural code generation - v3
Open access:

D3.9 PIACERE IDE - v3
Open access:

D4.3 Infrastructural model and code verification - v3
Open access:

D4.6 IaC Code Security and components security Inspection - v3
Open access:

D5.3 IaC execution platform prototype - v3
Open access:

D5.6 Canary environment prototype - v3
Open access:

D5.9 IOP prototype - v3
Open access:

D6.3 PIACERE run-time monitoring and self-learning, self-healing platform - v3
Open access:

D2.5 PIACERE DevSecOps Framework - v3
Open access:

D8.5 PIACERE IPR Management, Business models, and business plan v1
Open access: