The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "WI05 Unresponsive NGI escalation"
Jump to navigation
Jump to search
(Created page with "#mail #phone call") |
|||
| (14 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
# | {{Template:Op menubar}} {{Template:GO menubar}} | ||
# | |||
= Escalation procedure in case of unresponsive NGI = | |||
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 | |||
<br> | |||
[[Category:Infrastructure_Oversight]] | |||
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 • | EGI.eu Operations Team • | Regional Operators (ROD) |
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