Difference between revisions of "Regional Operator on Duty"

From EGIWiki
Jump to: navigation, search
(Alarms and tickets)
(Video tutorials)
Line 38: Line 38:
 
*[https://documents.egi.eu/document/301 Dashboard HowTOs and Training Guides]  
 
*[https://documents.egi.eu/document/301 Dashboard HowTOs and Training Guides]  
 
*[[FAQ Regional Operator on Duty|FAQ_Regional_Operator_on_Duty]]
 
*[[FAQ Regional Operator on Duty|FAQ_Regional_Operator_on_Duty]]
 
== Video tutorials  ==
 
 
*[http://www.youtube.com/watch?v=p-SrqJMDlOo 1. How to become a ROD member] - 7 steps which should be done to become a ROD member
 
 
*[http://www.youtube.com/watch?v=bNm4oupAmqI 2. Operations tools] - brief introduction of operations tools which a ROD mamber needs to perform duties
 
 
*[http://www.youtube.com/watch?v=rmgdaziDhUk 3. How to handle alarms] - an instruction how to manage alarms on the Operations Portal (ticket creation from an alarm, closing and masking alarms)  
 
 
*[http://www.youtube.com/watch?v=NKkbnwWnADw 4. How to handle tickets] - an instruction how to manage tickets on the Operations Portal (ticket creation, updating and closing tickets)
 
 
*[http://www.youtube.com/watch?v=5EEInTO2dVE 5. Issues escalated to COD] - an introduction of cases which are escalated to COD and how to deal with
 
 
*[http://www.youtube.com/watch?v=tsbcYoGNZls 6. Operations portal tools] - a brief introduction of the Operations Portal tools
 
 
  
 
== Resources  ==
 
== Resources  ==

Revision as of 13:37, 7 October 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) 



ROD

ROD (Regional Operator on Duty) is a role which oversees the smooth operation of Grid infrastructure in the respective NGI. ROD team is responsible for solving problems on the infrastructure within own Operations Centre according to agreed procedures. They ensure that problems are properly recorded and progress according to specified time lines. They ensure that necessary information is available to all parties. The team is provided by each Operations Centre and requires procedural knowledge on the process. The role is usually covered by a team or people and is provided by each NGI. Depending on how an NGI is organised there might be a number of members inthe ROD team who work on duty roster (shifts on a daily or weekly basis), or there may be one person working as ROD on a daily basis and a few deputies who take over the responsibilities when necessary. This latter model is generally more suitable for small NGIs.
In this text, the acronym ROD will be used both for the whole team, or for the person who is actually working on shift.
In order to become a ROD member, one first needs to go through the steps described in Joining operations.
The following text describes the duties that ROD (teams) are responsible for.

Duties

A list describing Duties.

Alarms and tickets

Information on how to deal with alarms raised in the Dashboard and how to generate and deal with tickets.

Downtimes

How downtimes are managed.

Communication

Communication channels for ROD to Sites and to management.

Security

How ROD should deal with security issues.

Manuals and procedures

In this section are linked manuals and procedures which RODs should be familiar with:

Resources