|D1.1: Quality Plan [M6]||This deliverable will describe the quality plan of the project and the required activities for the efficient implementation of the quality system. It will also include a simple but state-of-the-art risk management plan.|
|D1.2a/b/c: Project Periodic Report [M12/M24/M36]
||The specific reports will be submitted on an annual basis, providing information about the activities carried out by the Consortium, progress towards the project objectives, milestones and deliverables, problems encountered and corrective actions taken, actual usage of resources, and claim costs. The Project Periodic Reports will also describe the progress of the management activities carried out during each reporting period.|
|D2.1: User Requirements and Data Management Plan [M6]||This deliverable will report the requirements of the intended user groups that will drive the definition of E2Data architecture. Finally, the Data Management Plan will be released with any possible data releases, if possible, to the EU Open Data portal.|
|D2.2a/b: Intermediate Applications’ Definitions (software/report) [M12]||This deliverable will combine the current development state of the selected application (i.e. transition from scale-out execution mode to heterogeneous mode) along with an intermediate specification of the various kernels per application for heterogeneous execution. This information will drive the development of the lower-levels of the execution stack (WPs 3-5) in a data-driven manner. Following the initial implementation and evaluation of the application use cases, a revision of the development methodology will be conducted. The additional findings and/or corrections will be documented in D2.3.|
|D2.3a/b: Final Applications’ Definitions||Following the successful mid project checkpoint (M2.1), a final re-evaluation of the user and application requirements will be performed. Having an insight of the applications’ behaviour and performance, a thorough study regarding the successful achievement of their SLAs will be performed. Any additions to D2.2 will be performed and documented in this report along with final versions of E2Data’s use cases.|
|D3.1: Intermediate API Definition (report) [M18]||The intermediate API for both Big Data frameworks and Cloud Providers will be interally used for delivering D3.2.|
|D3.2: Cloud Software and Big Data Stack Implementation V1 (software) [M18]||
The E2Data Big Data (Apache Flink) and Cloud Provider (OpenStack) are partially operational enabling initial holistic evaluation of the platform (WP6).
|D3.4: Cloud Software and Big Data Stack Implementation V2 (software) [M30]||Regarding Apache Flink, this deliverableå will be realized through an external Java Archive (JAR) file with a properly and clean defined API for integration. In addition, documentation in the form of Java Doc will be provided for this package. With respect to OpenStack, this deliverable will be realized through a Linux open source install package that when applied to the target platform will install and make available the Delegator features and API available to the platform. This will include the API definition document in Linux man format.|
|D3.5: Visualization tool (software) [M30]||D4.1: The Intelligent Scheduler Definition (report) [M12]: The architecture of the E2Data Intelligent Scheduler is defined. The definition document will detail the interactions and APIs|
|D4.1: The Intelligent Scheduler Definition (report) [M12]||The architecture of the E2Data Intelligent Scheduler is defined. The definition document will detail the interactions and APIs|
|D4.2: The Intelligent Scheduler prototype V1 (software) [M18]||Report and Prototype of the first version of the E2Data Intelligent Scheduler. Includes the first version of the Intelligence layer as well as a first version of the hardware-aware, elasticity-driven Decision Making module.|
|D4.3: The Intelligent Scheduler prototype V2 (software) [M32]||Report and Prototype on the final version of the E2Data Intelligent Scheduler. Includes the final versions of the Intelligence, Decision Making and Scheduling modules of E2Data.|
|D5.1: Heterogeneous Execution Prototype V1 (software) [M18]||
Following the requirement analysis of the use cases, a number of the identified kernels will be offloaded and executed on CPU/GPGPU/FPGA/Xeon Phi units for both x86 and ARM architectures.
|D5.2: Profiling Tool (software) [M30]||
Based on deliverables from WP4 and WP5 the profiling compilation infrastructure along with the profiling history of the JVM will be implemented for all targeted architectures.
|D5.3: Heterogeneous Execution Prototype V2 (software) [M32]||Following the continuous requirement analysis of the use cases, all identified kernels will be offloaded and executed on CPU/GPGPU/FPGA/Xeon Phi units for both x86 and ARM architectures.|
|D6.1: E2Data architecture (report) [M12]||
A report analysing the way each of the E2Data’s components will interact with the standard platforms of choice along with the whole architecture.
|D6.2: Prototype V1 and preliminary evaluation (report) [M12]||
Initial prototype installation and standard benchmarking on x86 and ARM (CPU only).
|D6.3: Prototype V2 and intermediate evaluation (report) [M24]:||
Demonstration of the correct operation of entire E2Data system on large-scale data sets. Demonstration of the correct operation of heterogeneous accelerators on both x86 and ARM Architectures. Report on performance/power gains on available benchmarks and use cases.
|D6.4: Prototype V3 and final evaluation (report) [M36]||Demonstration of the correct operation of entire E2Data system on large-scale data sets. Demonstration of the correct operation of heterogeneous based accelerators on both x86 and ARM Architectures. Report on performance/power gains on all use cases and achievement of KPIs|
M7.1: Project’s web portal [M3]
M7.2: Project’s communication channels [M12]
|M7.3: E2Data workshop(s) [M12/M24/36]||TBA|