CORDIS

Combined final report of exploitation activities performed by the project across all WPs. Integrated plan for the INDIGO products exploitation beyond the end of the project.

Final report on software quality assurance, software maintenance and support, pilot infrastructure services and exploitation. Delivers the software quality control results, feedback from the 2ndt public software release, and related feedback from external infrastructures.

This deliverable contains the first report on the development of the toolkit (including APIs) and of the workflow services.

This report will confirm from the point of view of the research communities that the extended list of requirements specified in T2.1 and T2.2 has been taken into account in the INDIGO JRA development work.

The status report at M16 will report on the work done during the previous months to implement the first prototype of the PaaS layer, compared with the work plan and will provide an adjusted version of the work plan for the remaining 12 months of the project. This will be focused on describing the status of the first release of the PaaS architecture, and the adherence to the user-requirements

Reporting on the software QA, software maintenance and support, pilot infrastructure services and exploitation. Delivers the status and updated plans for these activities, software quality control results, feedback from the 1st public software release.

This deliverable contains the detailed design document and the resulting work plan of the technical area, compliant with the overall Technical Development Plan including WP4 and WP6.

Prepared in T2.4, after D2.2, it will cover the experience along the first half of the project, including detailed metrics on the impact based on direct indicators (website, questionnaires, participation in events, in particular training and specific workshops) and indirect ones (references to INDIGO solutions in different research communities websites, publications, etc.).

Assesses the probability and impact of risks occurring and to determine the appropriate type of risk response; defines a contingency plan if re-planning is not sufficient in face of the actual outcome of work performed and impact of related risks

This report will confirm from the point of view of the research communities that the initial requirements analysed in T2.1 and T2.2 have been taken into account in the design proposed by JRA for INDIGO solutions. Additionally, and based on the evolving experience and potential interest of the communities, an extended list will be provided to be taken into account in future developments and releases. This feedback will be provided to JRA workpackages.

This report will contain: • an overview of the progress of work towards the objectives of the action; • innovations achieved with respect to the state of the art; • feedback gathered via the communication activities; • the main results of the exploitation activities (when applicable); • a summary of the documentation produced by the project (including publications).

This report will contain: • an overview of the progress of work towards the objectives of the action; • innovations achieved with respect to the state of the art; • feedback gathered via the communication activities; • the main results of the exploitation activities (when applicable); • a summary of the documentation produced by the project (including publications).

This deliverable summarizes technological possibilities to integrate with other e-infrastructures including EGI, EUDAT, Helix Nebula, PRACE, Virtual Observatory. The analysis will contain description of means to exploit computational power from the external infrastructures and storage capacity as well. This document will contain detailed analysis of authorization and authentication problems and solutions crossing the borders of respective infrastructures

This deliverable contains the status report at M30 and will describe the work done during the previous 12 months, compared with the work plan provided with D4.3 and will give recommendation on future work in areas important to keep the achievements of this project sustainable

This report will contain: • an overview of the progress of work towards the objectives of the action; • innovations achieved with respect to the state of the art; • feedback gathered via the communication activities; • the main results of the exploitation activities (when applicable); • a summary of the documentation produced by the project (including publications).

This deliverable contains the status report at M18 and will describe the work done during the previous 12 months, compared with the work plan and will provide an adjusted version of the work plan for the remaining 12 months of the project.

Description of the software architecture and work plan for WP6

This deliverable contains the final report on the WP6 developments. It will also contain final user’s feedback including the metrics.

Provide an overview of the state of the art technologies used as base for the PaaS architecture. The technologies will be evaluated on the bases of the requirements coming from user-communities and on the requirement analysis from WP2 and WP6.

This deliverable will provide details of the use cases in T2.3 that have been originally defined and newly identified from the feedback of user communities (task 2.1) to test and monitor developments in WP3 (and WP6).

The report, within task 2.5 and following D2.6, will describe the formula, agreed with the different research communities, and with the consortium, to guarantee the support of INDIGO solutions. The potential exploitation impact will be based on usage statistics along the last six months of the project, after the last main software release. The analysis will be used to explore new projects or exploitation initiatives.

This deliverable will describe the general architecture of INDIGO produced by the collaborative work of WP4, WP5 and WP6. WP1 oversees the Technical Board of the project (see governance section) and therefore takes the responsibility of delivering the General Architecture deliverable on behalf of all the JRA work packages.

Second toolkits prototype evaluation report

Definition of the software QA tools, processes, procedures, roles and responsibilities and the related metrics and measurement methodologies. Software Maintenance and Support processes, roles and responsibilities. Definition of the pilot integration and testing infrastructures. Plan for liaison with external infrastructures and resource providers.

This report will detail the first results of the enquiring activities for the participating Research Communities or Infrastructures related to data ingestion, to be supported within INDIGO.

The status report at M30 will report on the work done to develop the last stable release of the PaaS layer and will give recommendations on future work in this area in order to keep the achievements of this project sustainable.

This report defines: quality processes (e.g. deliverable preparation, review preparation and post-review follow-up, activity-specific processes, etc.), tools and metrics, Monitoring of gender equality; Tracking of progresses.

This report from T2.2 will present the results of the different enquiring activities for each Research Community/Infrastructure about procedure details and parameters and it will include the specifications of INDIGO ingestion integrity test.

Assesses the probability and impact of risks occurring and to determine the appropriate type of risk response; defines a contingency plan if re-planning is not sufficient in face of the actual outcome of work performed and impact of related risks

This deliverable (in T2.3 and related to D2.3) will describe the additional use cases implemented during the project to test and monitor developments in WP3 and WP6, together with the monitoring tools and a report of their application

This report defines: quality processes (e.g. deliverable preparation, review preparation and post-review follow-up, activity-specific processes, etc.), tools and metrics, Monitoring of gender equality; Tracking of progresses.

This deliverable contains user’s feedback on the first Science Gateways and mobile apps release, including the metrics.

This report summarizes the findings of T2.1 and T2.2 along the first three months of the project, providing input to JRA activities. The report will be an integrated document including a general description of the research communities involved and of the use cases and workflows proposed and will express requirements captured, prioritized and grouped by technical areas (Cloud, HPC, Grid, Data Management, etc.). In particular, the analysis of Data Management Plans (DMPs) and data lifecycle documentation aiming to identify both synergies and gaps among the different communities will be provided.

The status report at M24 will report on the work done during the previous months to implement the second version of the PaaS layer, compared with the work plan and will provide an adjusted version of the work plan for the remaining months of the project. This will be focused on describing the status of the second release of the PaaS architecture, and the adherence to the user-requirements.

This report includes the complete dissemination plan for the project, prepared in T2.4, consolidating the initial plan discussed in the proposal, confirming the strategy and indicators, defining a calendar, and actions involving the different partners. The report also describes the first actions, including the launching of the project website and promotional material, and participation in general events.

This deliverable contains the detailed work plan of the technical area, compliant with the overall Technical Development Plan including WP5 and WP6. The plan is released early in the project life and updated every 12 months including a status report on the achievements of the past 12 months compared to the planned objectives

This deliverable will contain the evaluation of the available network orchestration tools, including the report on the interoperability of available “Software Defined Network” utilities and features.

This deliverable contains the software design document of the technical areas of WP4, compliant with the overall Technical Design Plan including WP5 and WP6. The design will be based on the requirement analysis from WP2.

Technical description of the first release of a Science Gateway prototype and release of the prototype for one selected mobile application.

Technical description of the second release of a Science Gateway prototype and release of prototypes for all selected mobile applications.

INDIGO-Datacloud: foundations and architectural description of a Platform as a Service oriented to scientific computing

Author(s): D. Salomoni, I. Campos, L. Gaido, G. Donvito, M. Antonacci, P. Fuhrman, J. Marco, A. Lopez-Garcia, P. Orviz, I. Blanquer, M. Caballer, G. Molto, M. Plociennik, M. Owsiak, M. Urbaniak, M. Hardt, A. Ceccanti, B. Wegh, J. Gomes, M. David, C. Aiftimiei, L. Dutka, B. Kryza, T. Szepieniec, S. Fiore, G. Aloisio, R. Barbera, R. Bruno, M. Fargetta, E. Giorgio, S. Reynaud, L. Schwarz, A. Dorigo, T. Bell, R. Rocha

Published in: arXiv.org (Cornell University Library), 2016

Author(s): G.C.P. van Zundert, J.P.G.L.M. Rodrigues, M. Trellet, C. Schmitz, P.L. Kastritis, E. Karaca, A.S.J. Melquiond, M. van Dijk, S.J. de Vries, A.M.J.J. Bonvin

Published in: Journal of Molecular Biology, Issue 428/4, 2016, Page(s) 720-725, ISSN 0022-2836

DOI: 10.1016/j.jmb.2015.09.014

Author(s): G.C.P. van Zundert, A.M.J.J. Bonvin

Published in: Journal of Structural Biology, Issue 195/2, 2016, Page(s) 252-258, ISSN 1047-8477

DOI: 10.1016/j.jsb.2016.06.011

Author(s): Dimitrios Spiliotopoulos, Panagiotis L. Kastritis, Adrien S. J. Melquiond, Alexandre M. J. J. Bonvin, Giovanna Musco, Walter Rocchia, Andrea Spitaleri

Published in: Frontiers in Molecular Biosciences, Issue 3, 2016, ISSN 2296-889X

DOI: 10.3389/fmolb.2016.00046

Author(s): Marcin Płóciennik, Sandro Fiore, Giacinto Donvito, Michał Owsiak, Marco Fargetta, Roberto Barbera, Riccardo Bruno, Emidio Giorgio, Dean N. Williams, Giovanni Aloisio

Published in: Procedia Computer Science, Issue 80, 2016, Page(s) 722-733, ISSN 1877-0509

DOI: 10.1016/j.procs.2016.05.359