1. Matthew Viljoen – EGI Foundation
OMB November 2018
Matthew Viljoen – EGI Foundation
EGI Operations Manger

2. Agenda
OMB

3. Introduction Long term monitoring alarms Next EGI Conference
BDII misconfiguration
Updates from EOSC-hub Operations
Onboarding overview
Service Management Board & Service Provider Forum
Regarding LOW level integration services
TRL Definitions for EOSC (TRL7,8,9)
Insert footer here

4. Long term monitoring alarms
Still some long-term monitoring alarms ongoing
New Ops campaign to reduce number
NGI managers please check
Problems? assistance? please contact
Insert footer here

5. Next EGI Conference – save the date!
6 – 8 May 2019, Amsterdam
Potential content for Ops
Operations Board Meeting F2F
NGI Lightning talks: plans, deployments (call to open)
Site Managers Lightning Talks: site manager updates, best practice?
Session on Notebooks: workshop on how to proceed with Notebooks, how  to build a service around them
Session on OneData: EGI infrastructure to support the DataHub
Session / working meeting with WLCG: potential topics: Rucio, HTC Condor - XDC / EGI workshop
Hackfest (open to cases to look at?)
Insert footer here

6. BDII misconfiguration
Top-level BDII has been creating multiple outgoing connections to port 2180 due to presence of flag:
OSG=True (should be set to: False)
Update to glite-info-update-endpoints package will be in UMD4 along with next few days along with regular UMD update
Insert footer here

7. Updates from EOSC-hub Operations
Onboarding overview
Service Management Board and Service Provider Forum
Regarding LOW level integration services
TRL Definitions for EOSC (TRL7,8,9)
Insert footer here

8. EOSC-hub Service Onboarding - overview
Document aiming to be overall(*) overview of the entire onboarding process
explaining target service catalogues, integration levels (LOW, MEDIUM, HIGH)
Completion of Service Description Template (SDT), validation steps and process steps
marketplace, operational integration (SMB/SP Forum)
Intended Audience?
Ourselves, achieving understanding of process, workflow & agreement across project
Prospective service providers (maybe add to website?)
(*) NOT exhaustive documentation of entire process!
Conceptual
With links to other content and more details elsewhere
Back in 2016 the Commission released a communication outlining the pilliars for an EUROPEAN CLOUD INITATIVE
European Open Science Cloud
European Data Infrastructure
Widening access and building trust
Including also SMEs and Industry
And identified some key challenges of this – lack of general awareness of the value of data; incentives for data sharing
Lack of common standards, lacking hardware, fragmentation & lack of coordination and need to translate recent changes in privacy & data protection to research data domain.
Later that year, the HLEG into the EOSC (setup in 2015) released recommendatations for addressing these key challenges and the problem statement (….)
Initial priority is finalizing onboarding of LOW level services

9. Service Management Board and Service Provider Forum
ToR now being finalized
Operations Coordination is critical; dedicated task for it (T4.1)
Aims (LOW,MEDIUM,HIGH)
communication
requirements
increasing awareness of services
access to users
Aims (MEDIUM, HIGH)
discussion of problems involving operations
discussion and approval of non-strategic changes to operational policies
onboarding process (operations)
Communication needs
Project
Service Providers
News
project news
major operational news
security threats
upcoming events
Increasing awareness of access enabling services
Requirements collection
General concerns
Feedback to project (SPs and users)
Back in 2016 the Commission released a communication outlining the pilliars for an EUROPEAN CLOUD INITATIVE
European Open Science Cloud
European Data Infrastructure
Widening access and building trust
Including also SMEs and Industry
And identified some key challenges of this – lack of general awareness of the value of data; incentives for data sharing
Lack of common standards, lacking hardware, fragmentation & lack of coordination and need to translate recent changes in privacy & data protection to research data domain.
Later that year, the HLEG into the EOSC (setup in 2015) released recommendatations for addressing these key challenges and the problem statement (….)

10. Service Management Board and SP Forum - Logistics
Service Integration Level(*)
Scalability is a concern
Need to reduce demands on peoples’ time to a minimum
Co-leadership (as with AMB)
SMB reports to AMB. Any strategic issues escalated to AMB
LOW
MEDIUM
HIGH
SP Forum
SMB
Virtual meetings (every 2-3 months, as needs be)
F2F meeting at EOSC-hub conferences
OPEN mailing list, indico category
Membership
All new SP reps join mailing list and encouraged to join virtual meetings
eInfras (EUDAT, EGI) represented collectively
Possible standing agenda items
Project news and upcoming events
Report from security team
Issues from SPs
Virtual meetings (every 1 months, as needs be)
F2F meeting at EOSC-hub conferences
CLOSED mailing list, indico category
Membership
eInfras (EUDAT, EGI) represented collectively
Possible standing agenda items
Problems/status reports from services that are not being dealt with by normal procedures
Policies which require changes/approval of non-strategic changes
Back in 2016 the Commission released a communication outlining the pilliars for an EUROPEAN CLOUD INITATIVE
European Open Science Cloud
European Data Infrastructure
Widening access and building trust
Including also SMEs and Industry
And identified some key challenges of this – lack of general awareness of the value of data; incentives for data sharing
Lack of common standards, lacking hardware, fragmentation & lack of coordination and need to translate recent changes in privacy & data protection to research data domain.
Later that year, the HLEG into the EOSC (setup in 2015) released recommendatations for addressing these key challenges and the problem statement (….)
(*) see D4.1

11. Regarding LOW level integration services
Consistent high level of service delivery - an important driver of EOSC-hub
LOW level services may:
have a less mature SMS and would like to develop it along with project participation
have a more mature SMS but be content with lower level of integration
(either way the SMS is out of scope from the purpose of onboarding)
not have any SLA defined. We can support it on defining an EOSC-hub ‘default’ SLA for new customers within EOSC-hub OR
already offer SLAs to its customers. Such SLAs are used for new customers within EOSC-hub
Back in 2016 the Commission released a communication outlining the pilliars for an EUROPEAN CLOUD INITATIVE
European Open Science Cloud
European Data Infrastructure
Widening access and building trust
Including also SMEs and Industry
And identified some key challenges of this – lack of general awareness of the value of data; incentives for data sharing
Lack of common standards, lacking hardware, fragmentation & lack of coordination and need to translate recent changes in privacy & data protection to research data domain.
Later that year, the HLEG into the EOSC (setup in 2015) released recommendatations for addressing these key challenges and the problem statement (….)

12. TRL Levels for EOSC
TRL 7 System prototype demonstration in operational environment
Service has passed through development and is an advanced stage of pre-production: the software is stable, reliable and has been deployed in an operational environment   
Functionality as required by the target users is documented, understood, validated with target sample users and accepted by them. Internal documentation exists regarding preliminary validation tests.
An assessment has been made of the required load of the system once the transition into production is complete and a plan has been made to service this load. This assessment has been documented.
An SLA is optional.
TRL 8 System complete and qualified
There are users who are making real use of the service and rely on it for their work.
Service documentation for end-users exists and is made available.
An acceptable use policy/terms of use is in place.
An SLA is in place, with service level targets defined and delivered service level targets periodically reported to the customer.  The existence of an SLA implies the following:
Basic (e.g. port up) and functional monitoring in place
Provision is made for user support, with response to incident and problem management is as per SLA
TRL 9 Actual system proven in operational environment
All requirements of TRL 8 are met.
Customer feedback is gathered and documented. The service has been in a production state and relied upon by users for at least 1 year and evidence is provided to show this.
There are quantitative outputs as a direct result of the service usage.
SLA is in place and monitored
Back in 2016 the Commission released a communication outlining the pilliars for an EUROPEAN CLOUD INITATIVE
European Open Science Cloud
European Data Infrastructure
Widening access and building trust
Including also SMEs and Industry
And identified some key challenges of this – lack of general awareness of the value of data; incentives for data sharing
Lack of common standards, lacking hardware, fragmentation & lack of coordination and need to translate recent changes in privacy & data protection to research data domain.
Later that year, the HLEG into the EOSC (setup in 2015) released recommendatations for addressing these key challenges and the problem statement (….)

13. Next OMB Next OMB To be confirmed on ML Thursday 17 Jan 10am CET?
My proposal would be to schedule the next one for Nov, if anything is urgent we can call one for oct.
OMB