Work Package 1

WP1 sets out the 'ethics requirements' that the project must comply with.

Work Package 2

WP2 deals with the overall architecture, and the identification of new features needed in order to support data-aware application modelling and multi-cloud deployment. This work package also identifies where in the PaaSage, CACTOS and PaaSword platforms the MELODIC contributions should be inserted, and how they will interplay with the existing technologies and components.

Work packages 3 and 4

WP3 and WP4 deal with upper ware and the execution ware respectively, in a way similar to the two layers of the PaaSage architecture. The upper ware uses and extends CAMEL with data flow modelling, and uses the combined information about the application structure, data structure, and data flow to develop a data aware reasoner to partition and locate the components across the best suited infrastructures. The execution ware enacts the actual deployment on multiple clouds, and monitors the running application, and its performance and use of data. The monitored information is used to automatically scale the application on a given cloud, or to request to the upper ware that the application deployment configuration is modified, and thereby also implementing cross-cloud scaling. WP4 will also need to develop mechanisms for deploying Hadoop and Spark transparently to the application, and deal with these frameworks as integral parts of the application’s execution environment.

Work package 5

WP5 starts off by defining the software quality and testing requirements, before it integrates the existing platforms from PaaSage, CACTOS, and PaaSword as the first MELODIC integration release. This release will be able to deploy applications cross-cloud and monitor them, but with no data-awareness. Thereafter it will continuously integrate new components being developed by WP3 and WP4 into the platform to the fully functional MELODIC data-aware releases. It will also maintain the link with the existing open source communities for the integrated platforms, and feed bug fixes and improvements back to PaaSage, CACTOS and PaaSword.

Work package 6

WP6 is responsible for the use cases and evaluation of the MELODIC platform. It will start off by identifying the applications’ requirements for data-aware multi-cloud execution, and the initial set of features the platform should provide to support these requirements. Then the applications will be implemented and modelled in the extended CAMEL to ensure that they are ready to be deployed by the integration release. Feedback will flow back to WP2-WP5 to improve and extend the feature set as new MELODIC releases are made available. Towards the end of the project, the use cases will be demonstrated to real potential customers to prepare for commercial use of the MELODIC platform beyond the end of the project.

Work package 7

WP7 deals with the outreach activities. In particular it will establish a sustainability plan for how to ensure that the MELODIC open source platform will be maintained and available beyond the project, and who will pay for the developers. The partners will develop their own exploitation ideas in this work package and align these with the sustainability plan. Finally, the work package will deal with communicating the project’s results to a wider audience, and disseminate the scientific gems to a more targeted community.

Work package 8

WP8 deals with the consortium management and external project representation, deliverable quality assurance, and risk management. Potentially this may lead to project re-planning as a WP8 activity.