This deliverable has been released in December 2022, at M36 of the project, and its main objective is to specify the final integration results between the PolicyCLOUD components. This deliverable will follow the methodology of D6.2 and D6.8 that were respectively submitted in M12 (December 2020) and M24 (December 2021) which have two main pillars: Define common practices for integration and validation of the outcomes of the project Detail the cloud environment the project will make use of to demonstrate the results Regarding the former, GitLab will be the base code repository for the project, where the project already owns an organizational account. Over GitLab [1], the trunk-based development branching policy has been applied, as we considered it the most suitable policy given the project characteristics. Also, GitLab’s issue reporting tool has been adopted, as it is fully integrated with GitLab’s features. The test bed to support the demonstrators has been deployed over EGI’s (EGI) infrastructure where flexibility is one of the critical features. This deliverable abstractly incorporates all the changes and implementations that WP2, WP3, WP4 and WP5 had made during the second year of the project. More details about the components and the actual implementation can be found in the related WP deliverables [7] [8] [9]. In detail, the schemas of the data have been finalized so the standard version that we defined initiated the data import to the repository of PolicyCLOUD. Moreover, the infrastructure (IaaS) and the platform deployment (PaaS/ Serverless) have been restructured and reshaped based on the latest needs of the components. EGI deployed the new flavour of PolicyCLOUD to the Openstack Infrastructure and IBM made the proper changes to the Openwhisk middleware for the serverless and other services. The related WP deliverables highlight detailed information and instructions for each component change that in total orchestrate the PolicyCLOUD engine.

This deliverable is submitted to the EC, not yet approved.