EOSC-hub receives funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No. 777536.

EOSC-hubbrief overview

24.1.2018 2

EOSC-hub mobilises providers from 20 major digital infrastructures, EGI, EUDAT CDI and INDIGO-DataCloud jointly offering services, software and data for advanced data-driven

research and innovation.

The context

24.1.2018 3

Project figures

• 100 Partners, 76 beneficiaries (75 funded)

• 3874 PMs, 108 FTEs, more than 150 technical and scientific staff involved– €33,331,18 of which the European Commission funds

€30,000,000

– €2,155,540 (~8 FTEs) are co-funded by the EGI Foundation and its participants + €1,221,094 (~5 FTEs) from EGI participants

• 36 months: Jan 2018 – Dec 2020 (18 month reporting period)

4

CSIC figures

• 8/13 WPs participation

• 3 task leadership– T3.2: Stakeholder Engagement Programme: EOSC-hub community– T6.3: Processing and Orchestration– T10.4: Common service building requirements and gap analysis

• 156PMs total

24.1.2018 5

Mission

The project will create the Hub, a federated integration and management system for the future EOSC

Resources and

Services

Federation “core”

services

Federated operations

Processes and

policies

24.1.2018 6

What does the Hub provide?

• Contact point for researchers and innovators to discover, access, use and reuse a broad spectrum of resources for advanced data-driven research➢ Catalogue of resources and services

➢ Humanities, Engineering, Medical and Health Sciences, Natural Sciences

• Corpus of policies, processes and federation services (community-defined)➢ Principles of engagement and EOSC “core” services

• Quality assurance reviews ➢ Manage end-to-end service level management performance

• Competence Centres and a Joint Digital Innovation Hub➢ Specialized Technical support, training

24.1.2018 7

Architecture

8

Backup slides

24.1.2018 9

Work packages

24.1.2018 10

From integration to utilization

Integrate production-r

eady services

Operate and Provide

Access and Consume

24.1.2018 11

Service Integration and Access Management

24.1.2018 12

Service Providers 1/2

e-Infra

EGI Federation

EUDAT CDI

Humanities

Language and literature (CLARIN)

Arts (DARIAH)

Engineering

Environmental engineering (sea vessels,

LNEC)

Civil Engineering

(Disaster Mitigation)

Medical and Health

Sciences

Biological Sciences (ELIXIR)

Structural biology

(WeNMR)

24.1.2018 13

Service Providers 2/2

Natural Sciences

Physical Sciences

• Astronomy (LOFAR)• Fusion (ITER)• High Energy Physics (CMS

and VIRGO)• Space Science (EISCAT-3D)

Earth Science

• EO Pillar• GEO• Climate Research (ENES)• Seismology (ORFEUS, EPOS)

Biological Sciences

• Marine and freshwater biology (IFREMER)

• Biodiversity conservation (LifeWatch)

• Ecology (ICOS)

24.1.2018

EOSC Domains and the Hub: what model?

EOSC Domain EOSC Domain

EOSC Domain EOSC Domain

Hub

14

24.1.2018 15

EOSC-hub Domain

• Manages

– The internal governance, strategy and funding

– The internal portfolio, policies and processes

• Participates in the Hub with

– Resources and services as needed

• Internally certified to comply to the Hub policies

– Input to the EOSC standards roadmap and policies

– Domain-specific FAIR implementation guidelines etc.

• The Hub is governed as a Commons

24.1.2018 16

Support to the Declaration: Governance and Funding

EOSC-hub– Provides an EOSC service integrator and federator.

– Develops the know-how and the prototype procurement and purchasing framework to acquire digital services from publicly funded infrastructures and commercial providers.

24.1.2018 17

Support to the Declaration: Data Culture and FAIR

EOSC-hub– Provides production-quality FAIR* data and services through

the participating Domains

– Ensures data can be used as widely as possible across scientific disciplines and between the private and public sector by

• Making core data resources discoverable and accessible

• Federating existing data infrastructures

* FAIR principles: a set of guiding principles to make data Findable, Accessible, Interoperable, and Re-usable.

24.1.2018 18

Support to the Declaration:Research Data Services and Architecture

EOSC-hub

– Realizes a system of EOSC domains

– Delivers the Hub as a delivery channel of resources and services

– Improves skills and knowledge among researchers and service operators by delivering specialised trainings and co-design

24.1.2018 19

Impact 1/4

• The operation of a federated European data and distributed computing infrastructure for research and education communities will optimise the access to IT equipment and services

– Creation of an EOSC-hub service portfolio, initially integrating EGI, EUDAT and INDIGO products

• Establishing partnerships with industrial and private partners

– Joint Digital Innovation Hub

24.1.2018 20

Impact 2/4

• Train people in research and academic organisations

– Training programme benefiting 20 research collaborations and external user groups

– Common and other federated services, data management planning, federated services management, domain-specific trainings (bioinformatics, marine, radio astronomy, seismology, language, earth observation, structural biology, coastal analysis, climate, high-energy physics, arts and humanities

24.1.2018 21

Impact 3/4

• Avoid the locking-in to particular hardware or software platforms

– Increase service interoperability by exposing well-defined interfaces based on open specifications that improve reusability

– Develop technical and service roadmaps to ensure a coherent evolution of the technical solutions and service offering

24.1.2018 22

Impact 4/4

• More scientific communities will use storage and computing infrastructures with state-of-the-art services

– Expand the access to services outside the traditional user base through the virtual access mechanism

– Stimulate engagement via Competence Centres in the following areas: life science, fusion, marine, radio astronomy, seismology, climate change, disaster mitigation

Relationship with EINFRA-21 projects

2324.1.2018

• FREYA: we already are requesting a BoF at RDA P11 with OpenAIRE, FREYA and EOSC-Hub to start discussing possibile room to discuss technical integration developments between the projects that are of relevance to RDA

• DEEP-HybridDataCloud: starts from INDIGO-DataCloud experience. Many parteners in common, an easy path to discuss with them. The focus on DL and ML could be of interest for many communities, so could help higher-level services in their implementation phase.

• XDC: starts from INDIGO-DataCloud experience. Focused on data management with a variety of use-cases with really high-level scale. This could help in improving the data-management and data-access facilities in the future for EOSC-Hub.

• We have to establish a contact with the other 3 projects to better evaluate their output and see if/how they could be useful for EOSC-Hub service catalogue

From WP10 presentation at the EOSC-hub kick-off meeting

24.1.2018 24

Areas of possible interaction

The most important Work Packages and Tasks, relevant for projects developing new services are:

• WP3, Task 3.2 (Stakeholder Engagement Programme: EOSC-hub Community)

• WP10, Task 10.2 (Service Catalogue Technical Evolution)

• WP10, Task 10.4 (Common service building requirements and gap analysis)

• WP4 (Federated Services Management)

24.1.2018 25

WP3, Task 3.2

Task 3.2 - Stakeholder Engagement Programme: EOSC-hub Community:

This task will identify prospective stakeholders and engage them into the EOSC-hub ecosystem through the model of Community as a “channel” used in large companies with a wide variety and complexity of services, partners and customers. The Community platform will provide a clear path to capture service integration and service level requirements for each stakeholder. It will also support, monitor and assess engagement with service providers.

• Task Leader: Isabel Campos, Fernando Aguilar

WP10 Tasks and activities

261/23/2018

WP leader and Technical coordinator: Giacinto Donvito

Tasks:

• T10.1 - Technical Roadmap: Giacinto Donvito, INFN

• T10.2 - Service Catalogue Technical Evolution: Mark van de Sanden, SURFSara

• T10.3 - Community Requirement Analysis and Technical support: Diego Scardaci. EGI.eu

• T10.4 - Common service building requirements and gap analysis: Pablo Orviz, CSIC

WP10, Task 10.2

2724.1.2018

• T10.2 - Service Catalogue Technical Evolution

– Definition of the project's Rules of Engagement (RoE), including guidelines, policies and procedures to assess conformance of services to the RoE and to the FAIR principles.

– Definition of appropriate procedures to assess the conformance of the candidate services to the RoE and to the FAIR principles and perform the assessment.

– Monitoring of the evolution of reference standards (and contribute where relevant) and track the evolution of the main software technologies in the Open Source communities. It also includes the evaluation of external technologies and software stacks that could be included into the Services Catalogue.

WP10, Task 10.4

2824.1.2018

• T10.4 - Common service building requirements and gap analysis

– Handling of requirements not addressable by a simple set of services already present in EOSC-hub service catalogue; deeper requirement analysis, considering external services or extending the EOSC-hub service catalogue

– review use cases from new communities. This does not apply to application level services.

– interaction with external entities, e.g. the EOSCpilot project or others Open Source projects, in order to assess the added value of their services, understand their impact on the current ones and finally propose new candidate services to be included into the project catalogue.

29

WP4 Federated Services Management - Overview

WP Leader: Matthew Viljoen, EGI.eu

Tasks:

• Task 4.1 - Operations Coordination & Supplier Relationship Management (SUPPM): Matthew Viljoen, EGI.eu

• Task 4.2 - Order & Customer Relationship Management (CRM) Giovanni Morelli, CINECA

• Task 4.3 - Service Availability and Continuity Management (SACM) and Capacity Management (CAPM): Alessandro Paolini, EGI.eu

• Task 4.4 - Information Security Management (ISM): David Kelsey, STFC

• Task 4.5 - Incident and Service Request Management (ISRM) and Problem Management (PM): David Vicente, BSC

• Task 4.6 - Configuration Management (CONFM), Change Management (CHM) and Release and Deployment Management (RDM): João Pina, LIP

30

WP4 Activities

Harmonization across EGI, EUDAT of Operations and Service Management

• Ensuring the provision of services within the catalogue. Harmonizing operational activities & ensuring interfaces between Service Providers (SPs) and the federation are in place and effective. Maintain policies and procedures to ensure quality of service, and validated by members of the Operational Advisory Board (OAB)

• Supplier management and ensuring existence of SLA/OLAs

• Customer management, provision of marketplace orders and after-sales support (e.g. customer satisfaction surveys)

• Service availability, continuity and capacity management

• Information Security Management, harmonization of policies and procedures

• Common helpdesks for incidents and service requests (1st, 2nd level support)

• Common configuration management, change management and release/deployment management

31

WP4: Operational Engagement with Technology Providers, SPs

Building on and harmonizing existing processes/good practice with EGI/EUDAT (specifics to be determined)

From Technology Providers, the following to be provided:

• software distribution channels/contacts

• support channels (e.g. ticketing system, response targets)

• minimum levels of documentation (high level/sysadmin-deployer/end-user)

(Other agreements are agreed with Service Providers via Operational Level Agreements)

Note that requirements driven technical innovation is done outside WP4.

32

On the XDC/DEEP side

Main items (to be understood/discussed):

• Involvement of user communities:

– New use cases/requirements?

→ How to interact to T3.2?

• Path towards the EOSC through EOSC-hub for the output of the two projects:

• Enhanced/extended INDIGO components already in the catalogue

• New components/services

– Pilots and Proof of concepts: are they part of XDC/DEEP activity plans?

– Integration with EOSC-hub: what does this mean?

– Who is in charge for this?

→ How to interact with WP10?

33

On the XDC/DEEP side

• From development to production

Two different roles:

- Service providers:

- Is there a relationship with XDC and DEEP?

- Product teams:

- Interaction with WP4 (third level of support)

34

Thanks for your attention