Action list review Room: 1/1-025

C-COD - ROD interactions Room: 1/1-025 proposal: C-COD should send e-mail to ROC manager (and CC to ROD) asking for *explanations* in case ROD failed to act. We think that sending an e-mail to ROD again does not make much sense as ROD *already* failed to deliver their service.

Requirements for new NGI to join EGI from Operational Support perspective Room: 1/1-025 What are the requirements for new NGI to join EGI from Operational Support perspective? A kind of operations SLA? - providing NOD (NGI Operator on Duty) service with specific rules on handling alarms and tickets - access to knowledge sharing DB or use of central GOC WIKI? - what else?

Quality metrics (NON-OK closed alarms) Room: 1/1-025 proposal: Eliminate possibility to close alarms in NON-OK state completely. Pass this functionality to C-COD. Make a procedure for ROD to "ask for closing". NON-OK cases: a) SD solution: freeze alarm. Problem: SD can be defined in past. -> Protest it! b) moving node out of production let dashboard check if the node is in production c) monitoring system problems - fake alarms due to failure of mon. infr. possibly this will not last longer than 72h. d) core service problems - add alarm for a core service and mask, - but what if the CS is not in our NGI? Create ticket in GGUS and assign an alarm to this ticket.

AOB Room: 1/1-025