1. EOSC Overall Architecture Donatella Castelli CNR-ISTI

2. EOSCPilot All Hands meeting, 8-9 March 2018, Pisa
Objective IT
From the EOSCPilot DoA
“This task develops the evolving EOSC overall Architecture, which will follow the “system of systems” approach and identifies the key components and services (and the relations among them) needed to:
make EOSC a system on its own
smoothly aggregate into a coherent whole the offerings, facilities and data of existing providers (including national and European e-Infrastructures, public cloud service providers, domain specific service providers like Research Infrastructures & EIROs),
offer advanced functionality realised by dynamically leveraging the aggregated constituents.”
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa

3. Preliminary step: EOSC conceptualization
Who is the EOSC IT «system» for?
What activities is the EOSC IT «system» expected to support?
Answering to these question has necessarility required a interpretation / conceptualization of EOSC
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa

4. EOSCPilot All Hands meeting, 8-9 March 2018, Pisa
The scenario
added value
Prerequisite: EOSC as a System-of-systems
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa

5. User roles (as they are now)
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa

6. EOSCPilot All Hands meeting, 8-9 March 2018, Pisa
Typical activities
Finding, accessing, reusing, depositing, publishing research artifacts, collaborating, open and track request for changes,…
Researchers
Monitoring reserach outcomes, assessing reserach impact, operating communication channels, open and track request for changes, ….
Research Administrators
Finding,accessing, using EOSC Servicesl managing SLAs, Providng feedback on EOSC services, open and track request for changes, ….
Third-party service providers
Managing the EOSC Service Component Provisioning, Managing the Data (Service) Provisioning, Managing the Underpinning Agreement, Developing an EOSC Service, …….
EOSC Supplier
Governing the EOSC system. Operating the EOSC system, Managing the EOSC Portfolio, Managing the EOSC Service, ….
EOSC System Managers
Activities are expected to fastly evolve, we have been quite conservative for the moment
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa

7. Added-Value Federation Models
Each EOSC service can be built by exploiting one or more components contributed by suppliers
Examples of federation models
Invisible coordinator
OneStopShop
MatchMaker
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa

8. Validation and Monitoring
Service Suppliers
On the Suppliers themselves, e.g. certified supplier, quality of the services above a given threshold,…..
Service-specific, e.g. any data repository must expose its content metadata using a format compatible with EDMI guidelines
End-users
On EOSC itself, e.g. any registered user can use EOSC services public interfaces
Service-specific, e.g. only authorised data curators can modify the content of the service Catalogue
Registration, validation and monitoring of services
Validation and monitoring of any PoE (SLAs, UAs)
Only placeholder services at the moment waiting for input by T2.1.3 and T5.3
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa

9. Service typologies identified so far
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa

10. EOSCPilot All Hands meeting, 8-9 March 2018, Pisa
Workplan for 2018
Refine and consolidate the EOSC system conceptualization/model
Select a number of services and specify their architecture /alternative architectures for them
e.g. service catalogue: centralised, distributed, replicated
Discuss deployment models for these services
e.g. Service catalogue: operated by a single entity? Replicas in Member States? Distributed in domain specific nodes?
(initial step for an Organizational architecture)
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa

11. Focus of the upcoming discussion
Contribute to the characterization and service classes by other WPs & Tasks
What services should be detailed?
How to address the deployment models?
Who can contribute to what?
Workplan
EOSCPilot All Hands meeting, 8-9 March 2018, Pisa