Meeting Access Information:
* Evo Client
Title: Pole1, Community: UNIVERSE
From: 14:00 CEST
To: 15:30 CEST
EVO gate click "Start" and browse the right link in the list ("Pole1").
* Phone call
Phone room ID: 37587
Phone password: 3376
EVO Phone Bridge Telephone Numbers:
Slovakia (UPJS, Kosice) +421 55 234 2420
Switzerland (CERN, Geneva) +41 22 76 71400
Italy (INFN, several cities) Phone numbers Enter '4000' to access the EVO bridge
Germany (DESY, Hamburg) +49 40 8998 1340
USA (BNL, Upton, NY) +1 631 344 6100
USA (Caltech, Pasadena, CA) +1 626 395 2112
Action list review5m
C-COD - ROD interactions20m
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 perspective20m
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)20m
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".
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.