Alert.png 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 "Regional Operator on Duty"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
{{Template:Op menubar}} {{Template:GO menubar}} {{TOC_right}}  
{{Template:Op menubar}} {{Template:GO menubar}} {{TOC_right}}  


= Introduction =
= ROD =


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.  
:'''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.


The purpose of this page is to collect in one place all materials related to ROD work.  
:In this text, the acronym '''ROD''' will be used both for the whole team, or for the person who is actually working on shift.


<br>
:In order to become a ROD member, one first needs to go through the steps described in [[Regional_Operator_on_Duty_welcome|Joining operations]].


'''If you are new in this activity please see first page '''[[Regional_Operator_on_Duty_welcome|'''ROD Welcome''']]
:The following text describes the duties that ROD (teams) are responsible for.


= People and Contact =
== [[ROD Duties|Duties]] ==


:A list describing ROD duties.
== [[ROD Alarms and tickets|Alarms and tickets]]  ==
:Information on how to deal with alarms raised in the Dashboard and how to generate and deal with tickets.
== [[ROD Downtimes|Downtimes]]  ==
:How downtimes are managed.
== [[ROD Communication|Communication]]  ==
The list of people responsible for NGI oversight and contact points can be found in [https://operations-portal.in2p3.fr/dashboard/regionalPreferences Operations Portal].  
The list of people responsible for NGI oversight and contact points can be found in [https://operations-portal.in2p3.fr/dashboard/regionalPreferences Operations Portal].  
To contact with all ROD teams can be used following mailing list where are subscribed all RODs' mailing lists:  
To contact with all ROD teams can be used following mailing list where are subscribed all RODs' mailing lists:  
*'''all-operator-on-duty''' AT mailman.egi.eu
*'''all-operator-on-duty''' AT mailman.egi.eu


= ROD duties  =
:Communication channels for ROD to Sites and to management.
 
The Regional Operations team is responsible for detecting problems, coordinating the diagnosis, and monitoring the problems through to a resolution. It monitors sites in their region, and react to problems identified by the monitors, either<br>directly or indirectly, provide support to sites as needed, add to the knowledge base, and provide informational flow to oversight bodies in cases of non-reactive or non-responsive sites. ROD is a team responsible for solving problems on the infrastructure 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 ROC and requires procedural knowledge on the process (rather than technical skills) for their work.  


All duties listed are mandatory for ROD team:<br>
== [[ROD Security|Security]]  ==


*'''Handling incidents '''- The main responsibility of ROD is to deal with incidents at sites in the region. This includes making sure that the tickets are opened and handled properly. The procedure for handling tickets is described in [[PROC01_Grid_Oversight_escalation|PROC01_Grid_Oversight_escalation]]<br>
:How ROD should deal with security issues.
*'''Propagate actions from COD down to sites''' - ROD is responsible for ensuring that decisions taken on the COD level are propagated to sites.
*'''Putting a site in downtime or suspend for urgent matters''' - In general, ROD can place a site in downtime (in the GOCDB) if it is either requested by the site, or 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 e.g. security incidents or lack of response.
*'''Notify COD about core or urgent matters''' - ROD should create tickets to COD in the case of core or urgent matters.


= Manuals and procedures  =
== Manuals and procedures  ==


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


*[[PROC01_Grid_Oversight_escalation|PROC01_Grid_Oversight_escalation]]  
*[[PROC01_Grid_Oversight_escalation|PROC01_Grid_Oversight_escalation]]  
*[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]]


Line 53: Line 56:
*[http://www.youtube.com/watch?v=tsbcYoGNZls 6. Operations portal tools] - a brief introduction of the Operations Portal tools
*[http://www.youtube.com/watch?v=tsbcYoGNZls 6. Operations portal tools] - a brief introduction of the Operations Portal tools


= Newsletter<br>  =
== Newsletter<br>  ==


A ROD Newsletter is periodically released since December 2010 to consolidate the Grid oversight teams (central and local ones). The purpose of this newsletter is to inform about recent and upcoming developments related to Grid Oversight and to show the support performance indicators during the month.&nbsp; <span lang="en" class="short_text" id="result_box"><span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">It</span> <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">is</span> <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">issued</span> <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">every month</span></span> and the information about new releases is sent to all RODs mailing list and to NGI managers.<br> The newsletters may be found at: https://documents.egi.eu/public/ShowDocument?docid=298  
A ROD Newsletter is periodically released since December 2010 to consolidate the Grid oversight teams (central and local ones). The purpose of this newsletter is to inform about recent and upcoming developments related to Grid Oversight and to show the support performance indicators during the month.&nbsp; <span lang="en" class="short_text" id="result_box"><span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">It</span> <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">is</span> <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">issued</span> <span class="hps" title="Kliknij, aby wyświetlić alternatywne tłumaczenia">every month</span></span> and the information about new releases is sent to all RODs mailing list and to NGI managers.<br> The newsletters may be found at: https://documents.egi.eu/public/ShowDocument?docid=298  


= ROD presentations  =
== ROD presentations  ==


This section is created to collect all ROD presentations which took place on our f2f meetings.  
This section is created to collect all ROD presentations which took place on f2f meetings.  


*[https://www.egi.eu/indico/getFile.py/access?contribId=210&sessionId=9&resId=0&materialId=slides&confId=207 NGI_IBERGRID]
*[https://www.egi.eu/indico/getFile.py/access?contribId=210&sessionId=9&resId=0&materialId=slides&confId=207 NGI_IBERGRID]


= Events  =
== Events  ==


Technical Forum 2012  
Technical Forum 2012  
*[https://indico.egi.eu/indico/contributionDisplay.py?sessionId=56&contribId=242&confId=1019 Grid Oversight Session]
*[https://indico.egi.eu/indico/contributionDisplay.py?sessionId=56&contribId=242&confId=1019 Grid Oversight Session]
Technical Forum 2011  
Technical Forum 2011  
*[https://www.egi.eu/indico/contributionDisplay.py?contribId=35&confId=452 Grid Oversight session]<br>
*[https://www.egi.eu/indico/contributionDisplay.py?contribId=35&confId=452 Grid Oversight session]<br>
User Forum 2011  
User Forum 2011  
*[https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=91&confId=207 ROD teams training session]  
*[https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=91&confId=207 ROD teams training session]  
*[https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=92&confId=207 Grid Oversight, ensuring the quality of the Grid infrastructure]
*[https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=92&confId=207 Grid Oversight, ensuring the quality of the Grid infrastructure]
EGI technical Forum 2010  
EGI technical Forum 2010  
*[https://www.egi.eu/indico/sessionDisplay.py?sessionId=117&confId=48#20100915 Grid Oversight, ensuring the quality of the Grid infrastructure]  
*[https://www.egi.eu/indico/sessionDisplay.py?sessionId=117&confId=48#20100915 Grid Oversight, ensuring the quality of the Grid infrastructure]  
*[https://www.egi.eu/indico/sessionDisplay.py?sessionId=116&confId=48#all Grid Oversight Training]
*[https://www.egi.eu/indico/sessionDisplay.py?sessionId=116&confId=48#all Grid Oversight Training]
ROD teams workshop Jun 2010  
ROD teams workshop Jun 2010  
*[https://www.egi.eu/indico/conferenceDisplay.py?ovw=True&confId=29 ROD teams workshop]
*[https://www.egi.eu/indico/conferenceDisplay.py?ovw=True&confId=29 ROD teams workshop]


= Resources  =
== Resources  ==


*[[Tools|Operations tools]]  
*[[Tools|Operations tools]]  

Revision as of 11:17, 14 February 2013

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 ROD 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

The list of people responsible for NGI oversight and contact points can be found in Operations Portal. To contact with all ROD teams can be used following mailing list where are subscribed all RODs' mailing lists:

  • all-operator-on-duty AT mailman.egi.eu
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:

Video tutorials

  • 2. Operations tools - brief introduction of operations tools which a ROD mamber needs to perform duties
  • 3. How to handle alarms - an instruction how to manage alarms on the Operations Portal (ticket creation from an alarm, closing and masking alarms)  
  • 4. How to handle tickets - an instruction how to manage tickets on the Operations Portal (ticket creation, updating and closing tickets)

Newsletter

A ROD Newsletter is periodically released since December 2010 to consolidate the Grid oversight teams (central and local ones). The purpose of this newsletter is to inform about recent and upcoming developments related to Grid Oversight and to show the support performance indicators during the month.  It is issued every month and the information about new releases is sent to all RODs mailing list and to NGI managers.
The newsletters may be found at: https://documents.egi.eu/public/ShowDocument?docid=298

ROD presentations

This section is created to collect all ROD presentations which took place on f2f meetings.

Events

Technical Forum 2012

Technical Forum 2011

User Forum 2011

EGI technical Forum 2010

ROD teams workshop Jun 2010

Resources