1. EGI Foundation (Session Chair)
EOSC Service Architecture and Portfolio Workshop
14-15 Sept Pisa
Sy Holsinger
EGI Foundation (Session Chair)
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

2. “Services for service developers and service providers” Session
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

3. Session Summary Brief introduction (10’) Open Discussion (40’)
Session topics
Overall goal of session
Relevant links to EOSC Architecture document
Open Discussion (40’)
Prepared questions as initial input
Additional questions that emerge
Discussion with live notes taken
Closing summary of key actions (10’)
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

4. Session Topics Main Topic Goal
Services for “service developers”, “service providers”, and “infrastructure providers”
Goal
Specify a list of services required from these 3 actors to be developed/delivered within the EOSC
Identify gaps to be filled (technical and human)
Define key actions (short- to medium-term)
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

5. Relevant Links to EOSC Architecture
2. Foundational principles
2.3 X-as-a-Service Provision Mode
2.4 EOSC Actor Roles
2.7 EOSC Abstract Services / Facilities
3. EOSC Reference Architecture
3.3 EOSC Services for Service Developers
3.4 EOSC Services for Service Providers
3.5 EOSC Services for Infrastructure Service Providers
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

6. 6 Actor Roles
Use functions and tools to perform their domain specific research activities and to collaborate
Develop new analytical models, new processes and tools to analyse data and derive knowledge
Develop services for scientists by understanding their requirements and the Open Science vision
Operate and provide access to their own portfolio of services according to declared SLAs
Provide access to computational, storage and network resources, according to declared SLAs
Facilitate the operation, assistance and quality assurance of the EOSC system and the coordination among its different stakeholders
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

7. Relevant Actor Roles Service Developers Service Providers
Develop the services that are used by the scientists.
Understand the requirements of the scientists and the Open Science vision and to implement services that support them.
Satisfy quality parameters, like usability, performance, reliability, economy, etc.
The spectrum covered by this role is wide going from IT professional experts to those deploying software in a cloud infrastructure.
Service Providers
Operate and provide access to their own portfolio of services according to declared service level agreements.
Infrastructure Service Providers
Provide access to e-Infrastructures, like those providing computational, storage and network resources, according to declared service level agreements.
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

8. Self-identification EOSC is not yet a “thing”
Hard to understand how the whole puzzle fits, and which piece each ”actor” represents and their connection to other pieces
Need a clear mapping in order for people to answer the “where am I?” question
What is needed and what can I offer?
Relates also to the use of “rules” for engagement
Without governance or ownership nothing can be “mandated”, therefore we should focus on “how” or ”methods” by which each actor can clearly engage with the EOSC
Many initiatives working in parallel, coupled with individual providers offering services to customers following their own policies, processes and procedures
Confusion over the term “cloud”
Hard ICT-infrastructure vs. metaphor for seamlessness and a commons (EOSC HLEG report)
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

9. The EOSC Architecture: EOSC-hub Perspective
Service Developers?
Service Providers?
Service Infra Providers?
Combination of the 3?
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

10. SIAM in EOSC-hub
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

11. FitSM: Lightweight Service Management
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

12. Conclusion Business oriented approach: Supply and demand
Service Catalogue (or marketplace) to discover and offer services is only one aspect
Both service developers and providers simply need to match needs and wants of customers – EOSC should facilitate this
Need to clarify this list of services
What services (maybe just service types) do the customers of the EOSC need and want
External Service Catalogue
What is required to facilitate the EOSC itself (federation services) = providers
Internal Service Catalogue
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

13. Questions for Discussion
What are the key services for: Service Developers?
What are the key services for: Service Providers?
What are the key services for: Infrastructure Providers?
How much of those technical services already exist? and is just a plumbing activity? Ifs so, who is providing them?
How much development is needed and in what areas?
EOSC-hub first step, so should include those but then also gaps
What “skills” should be the focus or are missing? Technical or Human?
e.g. in WP7, what should the training activity focus on? something like FitSM? or technical knowledge (EOSC HLEG says it’s not technical)
Does each role understand where they fit in the overall picture?
Mapping between roles and services -> “rules” of engagement (prefer more “methods”, ”rules” imply ownership/control/governance”
Is “Open Science” an important term when coming to labelling “developers” and “providers”? Do they identify as such?
What is the difference between Service Providers and Infrastructure Providers?
“IaaS-like” vs. “PaaS and SaaS-like”? Is this separation needed? More about service “categories”
Also to consider internal and external providers
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

14. Key Actions / Decisions..
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no

15. Thanks!
The European Open Science Cloud for Research pilot project is funded by the European Commission, DG Research & Innovation under contract no