Handling alarms and tickets
The main responsibility of ROD is to deal with alarms and tickets issued for sites in the region. This includes making sure that the tickets are created and handled properly. The procedure for handling tickets is described in the section on Dashboard.
Putting a site in downtime for urgent matters
ROD can place a site or a host in downtime (in the GOCDB) if it is either requested by the site, or if ROD sees an urgent need to put the site into downtime.
ROD may also suspend a site, under exceptional circumstances, without going through all the steps of the escalation procedure. For example, if a security hazard occurs, ROD must suspend a site on the spot in the case of such an emergency. It is important to know that COD can also suspend a site in the case of an emergency, for example as a result of a security incident or lack of response.
In both scenarios, it is important that communication channels between all parties involved are active.
Notify COD and EGI CSIRT about urgent matters
ROD should create tickets to COD in the case of urgent matters. For security related issues, ROD should also notify the CSIRT duty contact.
Summary of ROD duties
- Receive alarm notifications from sites in the scope
- Handle alarms less than 24 hours old
- Create tickets for alarms older then 24 hours that are not in an OK state
- Escalate tickets to COD if necessary (can be done directly through the Dashboard)
- Propagate actions from COD down to sites
- Monitor and update any GGUS tickets up to the solved status (via the Dashboard)
- Close alarms for solved problems
- Handle the final state of GGUS tickets not opened from the Operations Portal by marking them as verified.
- Put the site in downtime for urgent matters. Note: This is actually optional; an NGI may decide on a different policy if the site admins are not happy with ROD setting downtimes for them. However, it should be considered mandatory in case of urgent security incidents.
- Create tickets to COD for urgent matters