D2.1 System specification document

Download PDF »
Authors: Yiannis Verginadis, Wiktor Zolnieroiwcz, Paweł Skrzypek, Daniel Seybold, Kyriakos Kritikos, Somnath Mazumdar, Antonia Schwichtenberg, Feroz Zahid, Jörg Domaschka, Geir Horn, Ernst Gunnar Gran, Daniel Baur, Hynek Masata and Paweł Gora
Abstract

This document presents an initial system specification of the Melodic Multi-Cloud middleware platform. The document covers two important areas necessary for the subsequent development of the Melodic platform: Requirements Analysis and Technology Evaluation. The requirement analysis is essential to establish a set of initial features needed to realise an efficient middleware platform for Cross-Cloud dataintensive computing. At the same time, a complete evaluation of the available open technologies ensures that the efforts in the Melodic project are directed towards providing technology and tools that are currently beyond state-of-the-art and stateof-the-practice, and not on re-engineering solutions already available from other European and international open source projects. Based on the requirement analysis, considering both the perspective of the general data-intensive Cloud applications as well as the needs of the four Melodic use-cases, a set of functional and non-functional requirements are presented in this document. In addition, technical and business-level constraints imposed by private and public Cloud solutions are identified for the Melodic middleware platform. Moreover, a comprehensive technology evaluation comprising identification of reusable components from three identified EU projects (PaaSage, CACTOS, and PaaSword) and available big data technologies are presented in detail – together with the identified extensions needed for Melodic. The requirement analysis and the technology evaluation together resulted in a preliminary architecture of the Melodic middleware platform. This preliminary architecture, as presented in this document, will lay the foundation of the first Melodic release, the integration release, due by the end of the first year of the project.

D2.2 Architecture and initial feature definitions

The Architecture definition will detail and explain the overall architecture of the MELODIC middleware, and in particular describe the key components of MELODIC, and how these components are to interact and collaborate in order to realise an efficient multi-cloud middleware platform for data-intensive applications. In addition, the initial feature definition of MELODIC will be provided.

D2.3 Final framework and external APIs

This report will describe the final MELODIC framework and the external APIs for MELODIC, developed and defined as part of the iterative MELODIC development phases. The APIs represent the interfaces for developers to utilise the MELODIC middleware platform.

D2.4 Metadata schema

This deliverable provides scheme definitions, and detail related concepts regarding metadata management for both data stored in the cloud as well as user defined data annotations, including the security vocabulary needed to support appropriate access control mechanisms.

D2.5 Report on data placement and migration methodologies

This report will start with a review of existing data management techniques for clouds, before reporting on the novel MELODIC methodologies for data placement, data migration, and post-migration handling of data in a distributed multi-cloud infrastructure.

D2.6 Final features

This document will provide a comprehensive feature list of the complete MELODIC middleware platform, and conclude the last development phase for Architecture and Data management in correlation with the MELODIC final release, D4.09.

D3.1 Metadata schema management

A report on the first iteration of the MELODIC editor and the metadata schema management for maintaining all the MELODIC design-time artefacts. The necessary GUIs will be developed and made available to administrator(s) for editing and managing all the MELODIC models.

D3.2 Business logic for supporting the complete data and data-intensive application life-cycle management

An analysis of the MELODIC pre-migration, migration and post-migration phase methodologies to be considered for supporting the complete data and data-intensive application life-cycle management. It will provide the appropriate business logic for supporting this life-cycle management in distributed cloud environments.

D3.3 IDE-plugin for data-aware design and development of multi-cloud data-intensive applications

The first iteration of a design support tool for data-intensive application annotation will be developed in the form of a plugin for integrated development environments (IDE).

D3.4 Workload optimisation recommendation and adaptation enactment

A report on the research and development of an expert system that optimizes multi-cloud resources allocation through means of detecting reconfiguration opportunities and finding the optimal configuration in each situation. This work will constitute the first iteration of the MELODIC Reasoner.

D3.5 MELODIC Upper Ware

A report on the research and development of the MELODIC Adaptation Manager. In addition, it discusses the final iterations of all the relevant tools that constitute the MELODIC Upper Ware

D4.1 Provider agnostic interface definition & mapping cycle

This deliverable focuses on the provider agnostic interface definition and mapping to the system requirement analysis of D2.1. Representing the first iteration this definition and mapping cycle a first prototype of the provider agnostic interface mapper is developed. This prototype builds the starting point for the resource management framework and it is also evaluated against the the first draft of the resource management framework.

D4.2 Provider agnostic interface mapper

This deliverable describes the finalisation of the provider agnostic interface mapper. Basing on D3.1 and the validation with the first prototype of the resource management framework (D4.3) necessary refinements and extension are applied to the agnostic interface mapper.

D4.3 Resource management framework prototype

This deliverable focuses on the first prototype of the resource management framework. It revisits the provider agnostic interface definition to provide an interface for the Upperware, including management and monitoring capabilities. This first iteration of the resource management framework also includes the completed integration of PaaSage and CACTOS components.

D4.4 Resource Management Framework

This deliverable finalises the resource management framework. It revisits the prototype of D3.3 and refines the resource management framework due to lessons lerned during the development of the data processing layer and the Upperware. The resource management framework is evaluated using of the data processing layer.

D4.5 Data processing layer prototype

This deliverable describes the first iteration of the data processing layer resulting in a first prototype. Based on D4.1 and the parallel development of the rsource management framework it lifts a first data processing engine on top of the resource management framework and implements a first version of the data storage infrastructure. This first prototype is evaluated against the first iteration of use case implementation (D6.2).

D5.01 Integration and adaptation strategy

This deliverable will specify the requirements for adaptation of available OSS components. It will provide a catalogue of possible integration issues along with relevant mitigation measures.

D5.02 Updates to OSS frameworks

Download PDF »
Authors: Antonia Schwichtenberg, Katarzyna Materka, Kyriakos Kritikos, Paweł Skrzypek, Michał Semczuk
Abstract

The efficient and appropriate usage of existing opensource software in Melodic needs a careful study with respect to the changes and adaptations required for their integration with Melodic. This deliverable is aimed at identifying such changes. The frameworks reviewed in this deliverable include PaaSage and Cactus/Cloudiator. The review methodology is designed based on existing functional and non-functional features in each framework and the assessment of implementation code for each framework. The functional features are studied based on the objectives of Melodic: multi-cloud deployment of applications, cloud-agnostic description of applications and infrastructures, and support for data awareness and data locality, to name the most important ones. Performance, reliability, maintainability, and serviceability are among the important non-functional features considered in our methodology. The code assessment is performed by verifying the quality of the code against best programming practices as well as quality assurance requirements. We use the Clean Code approach as the best programming practice for evaluation.

D5.03 Security requirements & design

This deliverable will provide a specification of security requirements of the MELODIC framework and the design of the security technical component.

D5.04 Integration & testing requirements

Download PDF »
Authors: Antonia Schwichtenberg, Sébastien Kicin, Katarzyna Materka, Somnath Mazumdar, Jörg Domaschka, Yiannis Verginadis, Michał Semczuk, Paweł Skrzypek, Sebastian Schork
Abstract

A careful design of the Melodic integration strategy is very important as the main mission of Melodic is to integrate and adapt underlying frameworks, including PaaSage and CACTOS. This deliverable provides a detailed description of the requirements of this integration. The methodology for collecting integration requirements focuses on identifying the requirements separately for Control & Data Plane and Monitoring Plane. The other key set of requirements is functional testing and UI components testing, which specifies rules and conditions verifying the proper implementation of respective functional features of the Melodic system. The functional testing requirements are provided in the form of testing scenarios, which should be executed for a given Melodic release. These scenarios include initial deployment testing, global reconfiguration & local reconfiguration testing, metric management testing, reasoning related testing, and API testing. D2.1 "System specification" and use-case application descriptions are two main sources of identifying testing requirements. Apart from functional, also non-functional testing requirements are covered to verify the proper implementation of the nonfunctional features of the Melodic system. The nonfunctional testing scenarios include fault handling testing, performance testing, security testing, and other nonfunctional testing.

D5.05 Continuous integration platform & guidelines

This deliverable will provide a dedicated continuous integration platform for development and testing pourposes. It will also include guidelines for using the platform during development and testing process.

D5.06 Test strategy and environment

This deliverable will provide a description of platform testing strategy, detailed testing plan, the final version of the testing infrastructure and a set of test cases.

D5.07 Integration release and initial test environment

This deliverable will be the first release of integrated MELODIC framework. It will also provide a report of integration and technical testing activites (regression, funcionality, performance and security tests) based on test strategy and test plan included in D5.6 as well as the description of the initial version of testing infrastructure.

D5.08 Platform prototype release

This deliverable will be the second release of integrated MELODIC framework along with the security technical component. It will include the feedback from testing the v.01 release. It will also provide the report of integration and technical testing activites (regression, funcionality, performance and security tests) for release v.02 based on test strategy and plan included in D5.6.

D5.09 MELODIC final release

A report on the research and development of an expert system that optimizes multi-cloud resources allocation through means of detecting reconfiguration opportunities and finding the optimal configuration in each situation. This work will constitute the first iteration of the MELODIC Reasoner.

D5.10 Quality Assurance Guide

Download PDF »
Authors: Małgorzata Jakubczyk, Marcin Prusiński
Abstract

This document presents the most important processes and tasks related to Quality Assurance of software developed in Melodic. In particular, the document should be used as a manual for performing all activities within testing processes. Also it should be used in conjunction with the 'D5.06 Test Strategy and Environment' deliverable, which contains the strategy of testing, acceptance criteria, test related products and so on. The deliverable's intended audiences is as follows: It could be used by all participants in the project. Especially it shall be use by development teams (bugs handling process), test teams (bugs, test cases processes), architects (bugs, test cases processes), use case application users (test reporting, bugs handling) and management of the project (status of the testing of release). Altogether, the document is a complete and comprehensive manual for the most important software quality assurance tasks in the Melodic project.

D6.1 Evaluation Framework and Use Case Planning

This report will document the MELODIC evaluation framework, the validation scenario definitions and the organization and planning of the use case demonstrations.

D6.6 Guidebooks

This deliverable will comprise a practical guide for the transfer, application and deployment of MELODIC results in new and existing environments for practitioners from industry.

D7.1 MELODIC portal

The MELODIC portal will be an online space gathering all the parties interested in using the framework. It will include the repository with the open source code along with relevant technical documentation as well as explanation and education materials and tools for interaction with the community.

D7.2 Explanation and education materials

This deliverable will provide explanation and training materials supporting technical and business users of the framework and encouraging user participation.

D7.3 Dissemination and communication plan

This deliverable will provide a roadmap for the dissemination activities carried out by all partners throughout and beyond the project, including scientific publications, Internet, media and social channels.

D7.4 Report on dissemination and communication activities

This deliverable will report all the dissemination activities taken up during the project. It will include actions taken up by academic partners (list and brief presentation of scientific publications, list of scientific conferences and EC workshops attended) and commercial partners (list of trade fairs and brief presentation of activities using different communication channels specified in D6.3).

D7.5 Initial exploitation & sustainability plan

This deliverable will provide a draft plan for exploiting the MELODIC framework beyond the project. It will include both the individual exploitation strategies of the project partners and the joint strategy for the sustainability of the framework as a whole.

D7.6 Final exploitation & sustainability plan

This deliverable will provide an elaborated plan for exploiting the MELODIC framework beyond the project. It will include the specification of the lifecycle management methods & tools, sustainability model and licensing scheme as well as the individual exploitation strategies of the project partners.

D8.4 Final Report

This is a public report starting from the objectives, approach and challenges addressed by MELODIC, and documenting the resoults achieved, the lessons learned, and the recommendations for the future both with respect to technology, access and governance of the open source MELODIC platform, and promotes the use cases as examples for others to follow.