eosc-hub.eu
@EOSC_eu
EOSC-hub receives funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No. 777536.
Matthew Viljoen
WP4 Leader
Operational Requirements for
Entry into the EOSC-hub Service Catalogue
24/17/2018
Overview
• Outline of initial EOSC-hub WP4 discussions of operational
requirements for services to enter the EOSC-hub catalogue
• Forming input into D4.1 Operational requirements for the
services in the catalogue (M06, end Jun ‘18)
– input from WP4, 5, 6, 7, 13
– requirements likely to evolve – any feedback welcome
34/17/2018
TRL Requirements
44/17/2018
Entry into Service Catalogue
Pre-requisite for entry to Service Catalogue
Information required:
- Basic information
- Service classification
- Service support
- Contractual information
- Architecture
Work in progress – for more details see:
https://wiki.eosc-
hub.eu/pages/viewpage.action?spaceKey=EOSC&title=Service+Portfolio+Entry
+Template
5
Processes being setup as part of WP4
• SLM: Service provider identified and OLA setup
• SFRM: Supplier entered into the SFRM database
• CHM: Adoption of standard EOSC-hub risk calculation, use of CAB
for higher level risk changes etc.
• RDM: Integration into RDM (defined release processes etc.)
• Integration into EOSC-hub Operations processes (membership of
mailing list, service governance integration)
• SACM: define availability and continuity plan
• ISM (membership of mailing list, adherence to relevant ISM
policies
• CONFM: Add site information into a recognised database along
with appropriate configuration items
4/17/2018
Other EOSC-hub process integration
Service promotion
• ITSM processes instated in key e-
Infrastructures meeting FitSM requirements.
Each runs its own services
Some integration and interoperation
• Some services merged and run jointly with key
e-Infrastructures; others run separately.
Full service integration
• Shared policies, joint operational body
developing strategy + technical priorities.
EOSC-hub SMS* replacing existing key e-
Infrastructure SMSes
Levels of Integration (Processes and
Services) - ScenariosFederation type
Lose
Tight
*SMS = Service Mangement System, covering ITSM processes
7
EOSC-hub Internal Service
Catalogue
Set of supporting services
needed to poperate the
EOSC_hub & support the
delivery of its functions.
Cannot be ordered.
(e.g. EOSC-hub helpdesk,
marketplace etc.)
4/17/2018
Service catalogues
EOSC-hub Service
Catalogue
Set of services offered to
research communities
that can be ordered
(e.g. B2SAFE, EGI AppDB
VMops Dashboard

Operational Requirements for Entry into the EOSC-hub Service Catalogue

  • 1.
    eosc-hub.eu @EOSC_eu EOSC-hub receives fundingfrom the European Union’s Horizon 2020 research and innovation programme under grant agreement No. 777536. Matthew Viljoen WP4 Leader Operational Requirements for Entry into the EOSC-hub Service Catalogue
  • 2.
    24/17/2018 Overview • Outline ofinitial EOSC-hub WP4 discussions of operational requirements for services to enter the EOSC-hub catalogue • Forming input into D4.1 Operational requirements for the services in the catalogue (M06, end Jun ‘18) – input from WP4, 5, 6, 7, 13 – requirements likely to evolve – any feedback welcome
  • 3.
  • 4.
    44/17/2018 Entry into ServiceCatalogue Pre-requisite for entry to Service Catalogue Information required: - Basic information - Service classification - Service support - Contractual information - Architecture Work in progress – for more details see: https://wiki.eosc- hub.eu/pages/viewpage.action?spaceKey=EOSC&title=Service+Portfolio+Entry +Template
  • 5.
    5 Processes being setupas part of WP4 • SLM: Service provider identified and OLA setup • SFRM: Supplier entered into the SFRM database • CHM: Adoption of standard EOSC-hub risk calculation, use of CAB for higher level risk changes etc. • RDM: Integration into RDM (defined release processes etc.) • Integration into EOSC-hub Operations processes (membership of mailing list, service governance integration) • SACM: define availability and continuity plan • ISM (membership of mailing list, adherence to relevant ISM policies • CONFM: Add site information into a recognised database along with appropriate configuration items 4/17/2018 Other EOSC-hub process integration
  • 6.
    Service promotion • ITSMprocesses instated in key e- Infrastructures meeting FitSM requirements. Each runs its own services Some integration and interoperation • Some services merged and run jointly with key e-Infrastructures; others run separately. Full service integration • Shared policies, joint operational body developing strategy + technical priorities. EOSC-hub SMS* replacing existing key e- Infrastructure SMSes Levels of Integration (Processes and Services) - ScenariosFederation type Lose Tight *SMS = Service Mangement System, covering ITSM processes
  • 7.
    7 EOSC-hub Internal Service Catalogue Setof supporting services needed to poperate the EOSC_hub & support the delivery of its functions. Cannot be ordered. (e.g. EOSC-hub helpdesk, marketplace etc.) 4/17/2018 Service catalogues EOSC-hub Service Catalogue Set of services offered to research communities that can be ordered (e.g. B2SAFE, EGI AppDB VMops Dashboard

Editor's Notes

  • #8 internal – support delivery & coordination external – consumed by external customers/users