OMB November 2018 Matthew Viljoen EGI Foundation EGI

OMB November 2018 Matthew Viljoen – EGI Foundation EGI Operations Manger www. egi. eu This work by EGI. eu is licensed under a Creative Commons Attribution 4. 0 International License.

Agenda 10/16/2021 OMB 2

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

Long term monitoring alarms • Still some long-term monitoring alarms ongoing • New Ops campaign to reduce number • NGI managers please check https: //operationsportal. egi. eu/ • Problems? assistance? please contact operations@egi. eu 10/16/2021 Insert footer here 4

Next EGI Conference – save the date! https: //www. egi. eu/news/egi-conference-2019 -save-the-date/ • 6 – 8 May 2019, Amsterdam • Potential content for Ops Operations Board Meeting F 2 F 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 One. Data: EGI infrastructure to support the Data. Hub – Session / working meeting with WLCG: potential topics: Rucio, HTC Condor - XDC / EGI workshop – Hackfest (open to cases to Insert lookfooter at? )here – – 10/16/2021 5

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 UMD 4 along with next few days along with regular UMD update 10/16/2021 Insert footer here 6

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

EOSC-hub Service Onboarding - overview https: //confluence. egi. eu/display/EOSC/Service+Provider+Onboarding 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 • Initial priority is finalizing onboarding of LOW level services 8

Service Management Board and Service Provider Forum To. R now being finalized • Operations Coordination is critical; dedicated task for it (T 4. 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 nonstrategic changes to operational policies • onboarding process (operations) Communication needs Project • News - project news - major operational news - security threats - upcoming events • Increasing awareness of access enabling services Service Providers • Requirements collection • General concerns • Feedback to project (SPs and users) 9

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 SP Forum • Virtual meetings (every 2 -3 months, as needs be) • F 2 F meeting at EOSC-hub conferences • OPEN mailing list, indico category • Membership - All new SP reps join mailing list and encouraged to join virtual meetings - e. Infras (EUDAT, EGI) represented collectively • Possible standing agenda items - Project news and upcoming events - Report from security team - Issues from SPs LOW MEDIUM HIGH SMB Virtual meetings (every 1 months, as needs be) F 2 F meeting at EOSC-hub conferences CLOSED mailing list, indico category Membership - e. Infras (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 • • (*) see D 4. 1 https: //documents. egi. eu/public/Show. Document? docid=3342 10

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) • LOW level services may: • 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 11

TRL Levels for EOSC https: //confluence. egi. eu/display/EOSC/Service+Maturity+Classification • 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 12

Next OMB • Next OMB – Thursday 17 Jan 10 am CET? • To be confirmed on ML 10/16/2021 OMB 13