In this deliverable, we report on our key contributions towards the implementation and evaluation of the SODALITE platform and use cases. Whereas Deliverable D6.1 paved the way in M6 for the SODALITE platform by detailing the overall implementation plan and roadmap, we now report on the current status of implementation up to M12. Overall, the SODALITE development environment composed of the testbeds, repositories and the continuous integration and deployment platform are set up and made accessible to developers and use case owners. Further, initial releases and developments were achieved across all three key layers of the SODALITE platform according to the implementation plan up to M12. Finally, the three use cases of SODALITE are already ...
This document provides a wide view of the extent of communication and dissemination strategy of SODA...
This deliverable provides a description of the application layer software developed so far in the pr...
IoT-based applications need to be dynamically orchestrated on cloud-edge infrastructures for reasons...
In this deliverable, we report on our key contributions towards the implementation and evaluation of...
This deliverable presents the time plan for the development of the SODALITE platform, as well as the...
This deliverable reports on the development status after M12 of the SODALITE Runtime Layer and the i...
This deliverable presents the status of development of the Infrastructure as Code (IaC) layer within...
This document sets some rules and guidelines on how contributors can support the development of the ...
The SODALITE architecture is divided into 3 main layers: Modelling layer, Infrastructure as Code lay...
The UML use cases and the architecture presented in this deliverable have been defined with the cont...
We propose to tackle the complexity of deploying and operating modern applications onto heterogeneou...
We propose to tackle the complexity of deploying and operating modern applications onto heterogeneou...
SODALITE provides application for developers and infrastructure operators with tools that abstract t...
This open access book provides an overview of the work developed within the SODALITE project, which ...
The present deliverable reports on the work carried out within T3.1 “Application Semantic Modelling”...
This document provides a wide view of the extent of communication and dissemination strategy of SODA...
This deliverable provides a description of the application layer software developed so far in the pr...
IoT-based applications need to be dynamically orchestrated on cloud-edge infrastructures for reasons...
In this deliverable, we report on our key contributions towards the implementation and evaluation of...
This deliverable presents the time plan for the development of the SODALITE platform, as well as the...
This deliverable reports on the development status after M12 of the SODALITE Runtime Layer and the i...
This deliverable presents the status of development of the Infrastructure as Code (IaC) layer within...
This document sets some rules and guidelines on how contributors can support the development of the ...
The SODALITE architecture is divided into 3 main layers: Modelling layer, Infrastructure as Code lay...
The UML use cases and the architecture presented in this deliverable have been defined with the cont...
We propose to tackle the complexity of deploying and operating modern applications onto heterogeneou...
We propose to tackle the complexity of deploying and operating modern applications onto heterogeneou...
SODALITE provides application for developers and infrastructure operators with tools that abstract t...
This open access book provides an overview of the work developed within the SODALITE project, which ...
The present deliverable reports on the work carried out within T3.1 “Application Semantic Modelling”...
This document provides a wide view of the extent of communication and dissemination strategy of SODA...
This deliverable provides a description of the application layer software developed so far in the pr...
IoT-based applications need to be dynamically orchestrated on cloud-edge infrastructures for reasons...