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
 
(74 intermediate revisions by 8 users not shown)
Line 1: Line 1:
{{Template:Op menubar}}
{{Template:Op menubar}} {{Template:GO menubar}} {{TOC_right}}  
{{TOC_right}}


[[Category:COD]]
= ROD =
[[Category:ROD]]
= Introduction =


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 purpose of this page is to collect in one place all materials related to ROD work.


= People and Contact =
:'''ROD''' (Regional Operator on Duty) is a role which oversees the smooth operation of EGI 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 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:  
:In this text, the acronym '''ROD''' will be used both for the whole team, or for the person who is actually working on shift.
*'''all-central-operator-on-duty''' AT mailman.egi.eu


= ROD duties =
:In order to become a ROD member, one first needs to go through the steps described in [[Regional Operator on Duty welcome|Joining operations]].
All duties are detailed written in Operational Procedures for ROD document.


The main duties are:
:The following text describes the duties that ROD (teams) are responsible for.
* handling operations incidents (dashboard alarms)  
* handling operations tickets
* propagate information about core or urgent matters to COD
* putting sites in downtime for urgent matters


= Manuals and procedures =


In this section are linked manuals and procedures which RODs should be familiar with :
* [https://documents.egi.eu/public/RetrieveFile?docid=15&version=1&filename=OperationalProceduresforROD-v2.0.pdf Operational Procedures for ROD] (This is an old EGEE version of the document. Please keep in mind that some of information can be not relevant to EGI. There is still no EGI version of the document.)
* [https://wiki.egi.eu/wiki/Operations:COD_Escalation_Procedure COD Escalation Procedure]
* [https://documents.egi.eu/document/301 Dashobard Howto]


== Tutorial videos ==
'''Contact: '''all-operator-on-duty AT mailman.egi.eu <br>


* [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
== [[ROD Duties|Duties]]  ==
* [http://www.youtube.com/watch?v=bNm4oupAmqI 2. Operations tools] - brief introduction of operations tools which a ROD mamber needs to perform duties


= ROD performance - Operations Support Metrics=
:A list describing [[ROD Duties|Duties]].


* [[Grid_operations_oversight/OperationsSupportMetrics | Operations Support Metrics introduction]]
== [[ROD Alarms and tickets|Alarms and tickets]] ==
* 2011
** [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-January11.ods Jan]|[https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-February11.ods Feb]| [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-March11.ods Mar]
* 2010
** [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-May10.ods May] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-June10.ods Jun] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-July10.ods Jul] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-August10.ods Aug] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-September10.ods Sep] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-October10.ods Oct] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-November10.ods Nov] | [https://documents.egi.eu/secure/RetrieveFile?docid=155&version=1&filename=EGI-Operations_Support_Metrics-December10.ods Dec]


= Newsletter - New!=
:Information on how to [[ROD Alarms and tickets|deal]] with alarms raised in the Dashboard and how to generate and deal with tickets.
* [https://documents.egi.eu/secure/ShowDocument?docid=298 Document server: ROD newsletter]
* 2011
** [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%201-2011.pdf Jan] | |[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2002-2011.pdf Feb] | [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2003-2011.pdf Mar]
* 2010
** [https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2012-2010.pdf Dec]


= Events =
== [[ROD Downtimes|Downtimes]]  ==


User Forum 2011
:How [[ROD Downtimes|downtimes]] are managed.
* [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]


EGI technical Forum 2010
== [[ROD Communication|Communication]] ==
* [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]


ROD teams workshop Jun 2010
:Communication [[ROD Communication|channels]] for ROD to Sites and to management.
* [https://www.egi.eu/indico/conferenceDisplay.py?ovw=True&confId=29 ROD teams workshop]


= Resources =
== [[ROD Security|Security]]  ==


* [[Tools | Operations tools]]
:How ROD should deal with [[ROD Security|security]] issues.
 
== Manuals and procedures  ==
 
In this section are linked manuals and procedures which RODs should be familiar with:
 
*[[PROC01 Grid Oversight escalation|PROC01_Grid_Oversight_escalation]]
*[https://documents.egi.eu/document/301 Dashboard HowTOs and Training Guides]
**Webinar shortcuts.
**Introduction.&nbsp;
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=230 ROD duties ]
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=355 ROD – procedures&nbsp;]
**Becoming ROD team Member
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=427 Obtaining X509 certificate ]
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=496 Registration in GOCDB ] [https://www.youtube.com/watch?feature=player_detailpage&v=SBelpfcc00Y#t=690]
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=690 Registration in GGUS ]
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=747 Registration in dteam VO ]
**ROD shift
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=872 Dashboard overview ]
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=1493 Issues aka alarms ]
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=1967 Tickets ]
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=2232 Notepads ]
***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=2475 Handover ]
**Webinar Presentation
***[https://documents.egi.eu/public/RetrieveFile?docid=301&version=7&filename=ROD-webinar.pdf Slides]
*[[FAQ Regional Operator on Duty|FAQ_Regional_Operator_on_Duty]]
 
== Resources  ==
 
*[[Tools|Operations tools]]
*[[Operations Procedures|Procedures]]
 
[[Category:Infrastructure_Oversight]]

Latest revision as of 10:54, 30 March 2015

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 EGI 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.


Contact: all-operator-on-duty AT mailman.egi.eu

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