EGIIn SPIRE EGI Update T FerrariEGI eu WCLG

EGI-In. SPIRE EGI Update T. Ferrari/EGI. eu WCLG Ops Coordination Meeting 25 -04 -2013 12/16/2021 EGI-In. SPIRE RI-261323 1 www. egi. eu

Service Operations Security Policy 1/2 • Operations Management Board approved an extension for central emergency suspension of users – You must implement automated procedures to download the security emergency suspension lists defined centrally by Security Operations and should take appropriate actions based on these lists, to be effective within the specified time period. • Draft – https: //documents. egi. eu/document/1475 • Feedback by 03 -05 -2013 12/16/2021 EGI-In. SPIRE RI-261323 2 www. egi. eu

Service Operations Security Policy 2/2 • Next steps – Definition of a EGI CSIRT procedure for handling of compromised certificates and criteria for central emergency suspension (work in progress). See: https: //indico. egi. eu/indico/get. File. py/access? contrib. Id=5&res. Id=0 &material. Id=slides&conf. Id=1235 – Definition of policy enforcement plan • Requires the deployment of services for managing centrally lists and locally for managing suspension • Proposal: https: //indico. egi. eu/indico/get. File. py/access? contrib. Id=4&res. Id=0&m aterial. Id=slides&conf. Id=1233 12/16/2021 EGI-In. SPIRE RI-261323 3 www. egi. eu

New proposed GGUS workflows 1/2 • For handling of unresponsive submitters – Draft: https: //wiki. egi. eu/wiki/FAQ_GGUSWaiting-For-Submitter-Process – Tickets closed as unsolved in case of no reply to the ticket will be closed as unsolved by the GGUS monitoring team after 25 working days – tickets are closed only after human supervision • Feedback: 03 -05 -2013 EGI-In. SPIRE RI-261323 www. egi. eu

New proposed GGUS workflows 2/2 • For handling of unresponsive supporters – Draft: https: //wiki. egi. eu/wiki/FAQ_GGUSWaiting-For-PT-Process – Necessary for managing 3 rd level software support in a scenario with no central support coordination provided by EMI/IGE – Periodic notification to supporters when answer is awaited – Tickets closed as unsolved (after human supervision) after 30 working days EGI-In. SPIRE RI-261323 www. egi. eu

GGUS SUs • Revision of existing software support units and definition of software support contacts for each EMI and IGE product (in progress) – Reorganization within various EMI Product Teams EGI-In. SPIRE RI-261323 www. egi. eu

Differentiated quality of software support in GGUS 1/2 • No best effort support in GGUS • Three proposed types – to ensure response to tickets within a given time – to ensure that changes are delivered within a given ETA notification sent to supporters in case of violation • survey distributed to PTs in March – Collected input from most of the PTs – Most likely GGUS will support two types EGI-In. SPIRE RI-261323 www. egi. eu

Differentiated quality of software support in GGUS 2/2 • (A) Base support – Severity Level: 1 -4. Max response time: 5 w days working days • (B) Active support – Severity Level: top priority (1) and very urgent (2) - Maximum response time: 1 working day – Severity level: urgent (3) and less urgent (4) - Maximum response time: 5 working days • (C) Differentiated support – Severity Level: top- priority (1) - Maximum response time: 4 support hours Severity Level: very urgent (2) and urgent (3) - Maximum response time: 1 working day Severity Level: less urgent (4) - Maximum response time: 5 working days EGI-In. SPIRE RI-261323 www. egi. eu

GGUS Technology helpdesk after EMI and EGI • With the end of EMI/IGE existing open tickets will stay assigned to the existing Sus. No evidence of PTs currently active in GGUS that will stop providing support • ETAs will be requested for all RFCs regardless of priority • Ticket access rights – Submitter: rw – Support: rw to all supporters (currently it’s restricted) – All: r to all with access to GGUS • Dashboard will be provided to SUs to identify tickets requiring urgent response • No change foreseen for 1 st and 2 nd level support (provided internally by EGI) – Add information to tickets about RFCs that will be released in UMD EGI-In. SPIRE RI-261323 www. egi. eu

Software support after EMI • Product Teams being redefined – https: //twiki. cern. ch/twiki/bin/view/EMI/Emi. Product. Teams – Continuation of support of several products to be clarified for the after EMI phase • WMS (INFN), EMI-Common (INFN), EMI-Messaging, g. Lite-Infosys (CERN), WNo. De. S (INFN) • EMI-Common: EMI-UI, EMI-WN, g. Lite-yaim-core, Torque server config, Torque WN config, emi-nagios • g. Lite-Infosys: BDII core, BDII site, BDII top, lcg-info-clients – EGI will liaise directly with PTs to get information about release and software support plans discussion in progress with INFN EGI-In. SPIRE RI-261323 www. egi. eu

UMD 3. 0. 0 • Scheduled release date: May 13 th – Previously scheduled for the end of April – Delayed to include updates from CREAM and VOMS • Products from EMI-3 ready for UMD – WMS, UI, WN, L&B, DPM, ARGUS, Top/Site-BDII, GFAL, lcg_utils • Products still under verification/staged rollout: – APEL, proxy-renewal, CREAM, ARC stack • Products rejected: – VOMS 3. 0. 0, patch release expected for April 29 th – Sto. RM 1. 11. 0 EGI-In. SPIRE RI-261323 www. egi. eu