This deliverable will outline the commercial strategy for the AERO Project. This strategy is split into two parts. Firstly, the open-source strategy which will be applied to the open-source project outcomes. These account for the majority of the AERO outcomes, as this is a fundamentally open-source endeavour. However, there are also some proprietary solutions that complement these open efforts, led primarily by the industrial AERO partners (CPLAY, RHAT, SIPEARL, KTM, VOSYS, SED and UBI). These outcomes will have their own strategy that assists the open-source strategy of AERO.

An updated SWOT (Strengths, Weaknesses, Opportunities, Threats) analysis has been carried out to reflect the current strengths and weaknesses of the project’s exploitation efforts – namely that the very technical nature of the project will require some work to simplify, in order to then create convincing value propositions and benefits for both the open-source and commercial strategy of AERO. Additionally, the project outcomes in Section 2.4 have been updated to account for changes over the first 18 months of the project; specifically, the addition of Maestro and VOSySmonitor as two proprietary, commercial outcomes.

Finally, Section 4 of the deliverable reports on the efforts of CPLAY, RHAT and UNIMAN towards contributions to standards.

This document has the following four objectives:
1. To briefly describe the AERO communication and dissemination strategies, as these have already been defined in the DoA.
2. To present the AERO visual identity together with the AERO website and social networking channels.
3. To report the communication and dissemination activities that took place in the first 18 months of the project.
4. To present the current status of the project’s communication and dissemination KPIs.

Based on the presented KPIs we assess the project’s strategy and conclude that AERO is on the path to achieving its communication and dissemination goals.

The delayed delivery of the Rhea platform has triggered a series of mitigation actions. Specifically, as the targeted hardware is not yet available, the AERO partners have worked on the upbringing of their software components and technologies on alternative systems, as similar as possible to the Rhea platform. In addition, the consortium has modified the original workplan defined in the DoA, and initiated earlier the optimisation of the AERO software components (originally scheduled for the second half of the project).

These changes have caused a change also to the scope of this deliverable compared to its definition in the DoA. Thus, D6.2 has the following three objectives:
1. Provide an overview of the available alternative platforms and an updated roadmap for the delivery of the Rhea testbeds.
2. Discuss the project’s plan regarding overall integration and the status of the CI/CD platform.
3. Present the status at the time of writing of the various AERO software components and technologies, discuss the implementation and optimisation activities that have taken place until M18, provide any available evaluation results and describe next plans for the development/optimisation activities in the second half of the project.

Deliverable D5.1 presents the intermediate release of the AERO software artifacts developed until M18 under WP5. The goal is to optimize cloud management, deployment, monitoring, and orchestration services for the EU processor ecosystem.

The document is structured into three main sections:

– Section 2: Focuses on the MAESTRO cloud orchestration framework using Kubernetes for containerized applications.

– Section 3: Covers the ExaFlow/Knot frameworks, which accelerate cloud-based workflows and facilitate data science activities.

– Section 4: Discusses the deployment and optimization of a Function-as-a-Service (FaaS) platform.

Each section includes:
– An overview of software components
– Hardware and software specifications
– Building instructions
– Steps to run the software

This deliverable presents the intermediate release of the AERO software technologies that have been developed and optimized under the scope of WP4. This report aims to outline the work that has been carried out till M18 and show how potential users can reproduce the submitted artifacts for the tested hardware platforms. To that end, this report is structured in four main sections (Sections 2-5). Each section focuses on a specific technology, and aims to:
➢ Document the progress of the porting and optimization of the technology for a particular
tested platform that is similar to SIPEARL Rhea.
➢ Outline the hardware and software specifications of the tested platform and how the
technology is installed.
➢ Present a guideline for running specific tests and benchmarks on the tested platform.

This deliverable entails the intermediate software release (M18), along with the optimized software modules as emerged at the end of the baseline phase. This is work performed within Work Package 3. WP3 is composed of three tasks, namely T3.1 Operating Systems and Virtualization support, T3.2 Firmware and Drivers, and T3.3 Software/Hardware Security extensions.
This document presents work done by all tasks during the reporting period. Namely, with respect to T3.1, Section 2 presents operating system kernel work on Elastic Translations and Section 3 presents VOSySmonitor. With respect to T3.2, Section 4 presents the OpenCL driver for OneAPI Construction Kit. With respect to T3.3, Section 5 presents Homomorphic Encryption and the CKKS Benchmark. Section 6 presents work done on RISC-V virtualization.

This document has the following three objectives:
1. To describe the development and optimisation activities that have taken place until M18 towards the successful migration of the AERO pilots to the AERO envisioned platforms.
2. To present the plans for the development of the AERO pilots during the second part of the project.
3. To report initial performance evaluation results. Unfortunately, as the Rhea platform is delayed, runs have been executed on alternative ARM-based platforms, most notably an NVIDIA GraceHopper platform, as well as x86_64 platforms that serve as baseline.

AERO has a mission to develop and enhance an open-source software ecosystem designed to operate efficiently on the innovative processor architectures developed under the European Processor Initiative (EPI). This ecosystem integrates a range of advanced software components, including operating systems, virtualization technologies, and cloud software orchestration, while also enabling hardware acceleration for both native and managed programming languages. Achieving these ambitious goals requires diligent risk monitoring and assessment throughout the project. Effective risk management ensures that all partners are equipped to address any challenges or opportunities that may influence the attainment of AERO’s objectives. This deliverable extends deliverable D1.2 by elaborating on the project’s risk management during its
second year (M13-M24). Specifically, it provides an update regarding the status of the identified risks as of the end of the project’s second year and outlines the work plan adaptations that will be implemented by the consortium in the forthcoming period to mitigate the impact of those risks that have materialized.

This document describes the principles of the risk management plan that is followed by AERO. Additionally, it reports the risks of the projects that were initially described in the DoA together with new risks that have been identified during the first year of the project. For every registered risk, this deliverable presents the assessment of the impact that it may have on the project and any possible mitigation plans to mitigate it. Risk assessment is a continuous iterative process that involves all AERO partners. This document is a snapshot of that process.

Report of the requirements, technical specification and architecture as derived during the Compatibility phase of the project.

Report on the methodology and the techniques that will be used for gathering the user requirements, along with the results for understanding the needs and problems of the users and a description of the functional requirements, technological specifications the use case scenarios, along with the demonstration, validation, and evaluation of the project’s pilots.

Detailed report for the data management policy of the AERO project.

Description of the project management methodology, financial aspect, administrative forms, and templates for management of the project by all partners. It also describes the quality plan of the project and the required activities for the efficient implementation of the quality system.