EGI-Engage Competence Centres in EGI-Engage Gergely Sipos WP6 ‘Knowlegde Commons’ coordinator 6/14/2016 1

EGI-Engage and WP6 The generic process of CCs Administrativa – timing, deliverables Suggested working practices Support services for CCs TODOs

EGI-Engage and WP6 EGI-Engage 43 partners (35 funded), 1161 PMs, 30 months 8m Euro EC contribution 6/14/ WP6 Knowledge Common includes Competence Centres to link EGI and RIs: ELIXIR, BBMRI, INSTRUCT and VPH (MoBrain), DARIAH, LifeWatch, EISCAT_3D, EPOS, Disaster mitigation (AsiaPacific) Project start date: 1 st of March 2015

Competence Centres Technical support to eight user communities and RIs on the ESFRI roadmap to foster the adoption of state-of-the-art services and evolve them according to their requirements. The support will be delivered through a network of Competence Centres with the participation of user communities, technology providers and NGIs/EIROs, OSG and Asia Pacific 4

Competence Centre objectives BBMRI: data and compute infrastructure that will allow a biobank federation for the storage of big data, parallel data analysis (EGI/EUDAT pilot) DARIAH: federated cloud storage for high availability of data exploitation, science gateway (grid&cloud), real-time search application EISCAT_3D: archiving and processing of data (joint EGI/EUDAT pilot) ELIXIR: enable a federated data analysis infrastructure for representative use cases EPOS: AAI, IaaS/PaaS/SaaS federated cloud services for data exploitation Structural biology/INSTRUCT: computation services for big data LifeWatch: Processing tools for biodiversity data, depositing of citizen scientist data, on demand virtual laboratories in the federated cloud Disaster Mitigation: Enable applications from this domain on DCIs and facilitate access through gateways

Infrastructure priorities Research questions Domain solutions Research infrastructures and communities EGI community solutions High Throughput Computing Federated Cloud AAI Data management Job/task management Training and support … The generic process Use case and requirement collection Solution and use case analysis System specification Development Evaluation and release Training, support, dissemination Approx. M1-6

Timing of WP6 tasks ELIXIR SA2.3 BBMRI SA2.4 MoBrain SA2.5 DARIAH SA2.6 LifeWatch SA2.7 EISCAT_3D SA2.8 EPOS SA2.9 Disaster Mitigation SA2.10 M6M24M16M1M30 Training Technical User Support SA2.1 SA2.2 Life sciencesHumanities Environmental sciences Generic Mar’15Aug’15Jul’16Mar’16Sep’16 To be discussed TBD

Formal Deliverables M1-15 CodeDateTitleTypeOwner D6.1M9Assisted pattern recognition tools integrated with EGI for citizen science OTHLifeWatch D6.2M11Data repository for DARIAHOTHDARIAH D6.3M11Production portal for EISCAT_3DOTHEISCAT_3D D6.4M12Fully integrated MoBrain Web portalOTHMoBrain D6.5M12Final version of Multi-Source Distributed Real-Time Search and Information Retrieval application OTHDARIAH D6.6M12Data flow handler and basic R tools to integrate and process data from Ecological Observatories on EGI DEMLifeWatch D6.7M13Implementation and evaluation of AMBER and/or GROMACS on the testbed(s) REPMosGrid D6.8M14Analysis of requirements on biobank and study workflowsREPBBMRI D6.9M14Web portals for tsunami wave propagation simulations and for WRF- based weather simulation OTHDisaster Mitigation D6.10M15Infrastructure tests and best usage practices for life science service providers REPELIXIR D6.11M15Security toolset release for BBMRI-ERICOTHBBMRI + Milestones to support reaching these deliverables

Formal Deliverables M16-30 CodeDateTitleTypeOwner D6.12M16GPGPU-enabled web portal(s) for MoBrainOTHMoBrain D6.13M18EPOS EGI pilot incorporating data retrieval, transfer and linkageDEMEPOS D6.14M21Scipion cloud deployment for MoBrainOTHMoBrain D6.15M24Demonstrator for ELIXIR workflows implemented in the EGI Federated cloud DEMELIXIR D6.16M24Evaluated cloud environment and demonstrator of analysis workflow for biobank studies DEMBBMRI D6.17M24Production level gateway for Arts and HumanitiesOTHDARIAH D6.18M24Report on the installed LifeWatch applications and their usage recordREPLifeWatch D6.19M24EPOS EGI pilot integrating computational resources and servicesDEMEPOS D6.20M24Application of the simulation portals for scientific scenario in disaster mitigation DEMDisaster mitigation D6.21M28Second version of enhanced portal for EISCAT_3DOTHEISCAT_3D D6.22M29Design larger scale multi-hazards simulation attempting to reduce the uncertainty of climate change assessment DEMDisaster mitigation D6.23M30Report on evaluation of EPOS EGI pilot studiesREPEPOS

Concept of interest groups Virtualisation and cloud CC1CC2CC3CC4 CC5 CC6CC7CC8 GPGPUs Open Data AAI Interest group 1 Interest group 2 Interest group 3 Interest group 4...

Suggested working practices list and Wiki page for each CC Detailed workplan into Wiki – at least about M1-12 period With focus on milestones, deliverables – both internal and external Regular telcos arranged by CC coordinator (monthly?) Openness Integrate unfunded contributions from the NGIs and the Ris Kick-off meetings – separately for each CC during March/April At location of your choice To discuss CC-specific tasks With EGI contributions about technical topics of your preference All-hands meetings 2 meetings per year for all CCs – to harmonise roadmaps, to form interest groups Co-located with EGI forums/conferences (May and October 2015)

Support services for CCs lists – to be created  CC coordinators –  One list for each CC – managed by Wiki based CC pages: One page to be created per CC – editing right linked to cc-xxx group Webex: 2 rooms, max 25 people at a time Booking information will be circulated to CC-coordinators Indico: New folder to be created for CC events Document Database: You can use it to manage and share documents (any file) Requirements Tracker: CC-specific queues and web gadgets can be created EGI Website New section for CCs to be created.

TODO 1.Confirm coordinator (and optionally technical coordinator) contacts Gergely to circulate the initial list Gergely to setup the coordinators list 2.Send the list of CC members to Gergely (with addresses) Gergely to setup the CC-specific lists 3.Gergely to allocate one Wiki space for each CC Move the detailed CC workplan onto these public pages 4.Decide about CC kick-off meeting Topics, agenda, location, date Co-location with community event? Co-location with EGI Conference? (limited time) 5.Planning for EGI Conference Feed your input through the PC