Latest revision as of 14:47, 26 November 2014

Main

EGI.eu operations services

Support

Documentation

Tools

Activities

Performance

Technology

Catch-all Services

Resource Allocation

Security

EGI Infrastructure Operations Oversight menu:

Home •

Escalation procedure in case of unresponsive NGI

In case of not responding NGI:

1st notification in GGUS
(after a week) 2nd notification + NGI manager list (from GOC DB) in 'Involve others' in GGUS
(after a week) email to operations@egi.eu
Operational escalation by Malgorzata K
Political escalation by Peter S

@@ Line 1: / Line 1: @@
-{{Template:Op menubar}}
+{{Template:Op menubar}} {{Template:GO menubar}}
-{{Template:GO menubar}}
-[[Category:Grid Oversight]]
-= Escalation procedure in case of unresponsive NGI =
+= Escalation procedure in case of unresponsive NGI  =
-In case of not responding NGI, COD should:<br>
+In case of not responding NGI:<br>
+# 1st notification in GGUS
+# (after a week) 2nd notification + NGI manager list (from GOC DB) in 'Involve others' in GGUS
+# (after a week) email to operations@egi.eu
+# Operational escalation by Malgorzata K
+# Political escalation by Peter S
-#Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from [http://tinyurl.com/724emw5 GOC&nbsp;DB - NGIs List] or from Dashboard)
+<br>
-#If no answer after 3 working days, make a phone call to NGI&nbsp;manager (phone number can be found in GOC&nbsp;DB&nbsp;- look at given NGI's detailes - do not forgot about time zones&nbsp;;) . If first one was unsuccesful please make a second call.
+[[Category:Infrastructure_Oversight]]
-#If that doesn't help, set the ticket assigned to NGI to unsolved and create a new ticket to COO&nbsp;with full report about the situation.
-<br>