MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Regional_User_Documentation",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/postorius/lists/mediawiki-api-announce.lists.wikimedia.org/> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "922": {
                "pageid": 922,
                "ns": 0,
                "title": "Regional Operator on Duty",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "{{Template:Op menubar}} {{Template:GO menubar}} {{TOC_right}} \n\n= ROD  =\n\n\n\n:'''ROD''' (Regional Operator on Duty) is a role which oversees the smooth operation of EGI&nbsp;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.\n\n:In this text, the acronym '''ROD''' will be used both for the whole team, or for the person who is actually working on shift.\n\n:In order to become a ROD member, one first needs to go through the steps described in [[Regional Operator on Duty welcome|Joining operations]].\n\n:The following text describes the duties that ROD (teams) are responsible for.\n\n\n\n'''Contact: '''all-operator-on-duty AT mailman.egi.eu <br>\n\n== [[ROD Duties|Duties]]  ==\n\n:A list describing [[ROD Duties|Duties]].\n\n== [[ROD Alarms and tickets|Alarms and tickets]]  ==\n\n:Information on how to [[ROD Alarms and tickets|deal]] with alarms raised in the Dashboard and how to generate and deal with tickets.\n\n== [[ROD Downtimes|Downtimes]]  ==\n\n:How [[ROD Downtimes|downtimes]] are managed.\n\n== [[ROD Communication|Communication]]  ==\n\n:Communication [[ROD Communication|channels]] for ROD to Sites and to management.\n\n== [[ROD Security|Security]]  ==\n\n:How ROD should deal with [[ROD Security|security]] issues.\n\n== Manuals and procedures  ==\n\nIn this section are linked manuals and procedures which RODs should be familiar with: \n\n*[[PROC01 Grid Oversight escalation|PROC01_Grid_Oversight_escalation]] \n*[https://documents.egi.eu/document/301 Dashboard HowTOs and Training Guides] \n**Webinar shortcuts. \n**Introduction.&nbsp; \n***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=230 ROD duties ] \n***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=355 ROD \u2013 procedures&nbsp;] \n**Becoming ROD team Member \n***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=427 Obtaining X509 certificate ] \n***[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] \n***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=690 Registration in GGUS ] \n***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=747 Registration in dteam VO ] \n**ROD shift \n***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=872 Dashboard overview ] \n***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=1493 Issues aka alarms ] \n***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=1967 Tickets ] \n***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=2232 Notepads ] \n***[https://www.youtube.com/watch?feature=player_detailpage&v=pJsCx5sj9Uc#t=2475 Handover ] \n**Webinar Presentation \n***[https://documents.egi.eu/public/RetrieveFile?docid=301&version=7&filename=ROD-webinar.pdf Slides] \n*[[FAQ Regional Operator on Duty|FAQ_Regional_Operator_on_Duty]]\n\n== Resources  ==\n\n*[[Tools|Operations tools]] \n*[[Operations Procedures|Procedures]]\n\n[[Category:Infrastructure_Oversight]]"
                    }
                ]
            },
            "1591": {
                "pageid": 1591,
                "ns": 0,
                "title": "Regional Operator on Duty welcome",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "{{Template:Op menubar}} {{Template:GO menubar}} {{TOC_right}} \n\n= Welcome on board!<br>  =\n\nDear ROD member, <br> \n\nthis page was created to help you<span lang=\"en\" class=\"short_text\" id=\"result_box\"><span class=\"hps\" title=\"Click for alternate translations\"> start with ROD duties. We will show you briefly what you should do to prepare yourself to act as a ROD.\n</span></span> \n\n<span lang=\"en\" class=\"short_text\">\n</span> \n\n<span lang=\"en\" class=\"short_text\"><span class=\"hps\" title=\"Click for alternate translations\">First, in section \"How to become a ROD member\" we will describe steps which needs to be taken before you start your work. In section \"ROD duties\" you will find all </span></span><span lang=\"en\" class=\"short_text\" id=\"result_box\"><span class=\"hps\" title=\"Click for alternate translations\">the tasks</span> <span class=\"hps\" title=\"Click for alternate translations\">that make up the</span></span> ROD duties. Section \"Important to read\" states a short introduction of all documents which concern this activity and which you are supposed to read at the beginning. Under \"Tools\" section will be described all tools used by ROD teams. Finelly,&nbsp; \"Contact\" section is going to inform you how to contact others.<br> \n\n== How to become a ROD member<br>  ==\n\nThere are few actions which needs to be taken before you start your work: \n\n#'''Get a valid grid certificate delivered by certifiation authorities''' - this step is important because most of the tools used during the shift require certificate. [http://www.eugridpma.org/members/worldmap/ Find] EUGRIDPMA members. <br> \n#'''[https://voms.hellasgrid.gr:8443/voms/dteam Register] to Dteam VO''' - Dteam membership will give you possibility to test sites and debug problems.<br> \n#'''[https://ggus.eu/index.php?mode=register_info Register] into GGUS tool as support staff''' - GGUS is a ticketing system which is used for operational purpose within EGI. With support staff role you will be able to reply on and update recorded tickets.<br> \n#'''[https://goc.egi.eu/portal/index.php?Page_Type=Role_Requests Register] in GOC DB tool''' - GOC DB is a central database which contains all the information about EGI grid infrastructure (sites and people). To be ROD members you have to be recoreded in this  database. It will allows you to perform step 5.<br> \n#'''Request the Regional Staff role in the GOC DB''' - Thanks to this role you will be recognized automatically in operations tools as ROD member. It gives you a several privilages in the database as well as in other tools.<br> \n#'''Contact your NGI manager''' - you need to contact your<span style=\"font-weight: bold;\"> </span>NGI manager to be approved in GOC DB as Regional Staff and to be added to ROD mailing list in your NGI (this mailing list is a contact point to the whole ROD team within the NGI). \n#'''Get familiar with the ROD wiki page''' - [[Regional Operator on Duty|ROD wiki page]] is a single place where you will find all information relevant to your work as a ROD.<br>\n\n<br> \n\nTo see how to perform all those actions please watch video [http://www.youtube.com/watch?v=p-SrqJMDlOo How to become a ROD member] (7 steps which should be done to become a ROD member also )\n\n== ROD duties<br>  ==\n\nThe 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 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 Operation Center and requires procedural knowledge on the process (rather than technical skills) for their work. \n\nAll duties listed are mandatory for ROD team:<br> \n\n*'''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|EGI Infrastructure Oversight escalation procedure]]<br> \n*'''Propagate actions from EGI Operations / Operations Support down to sites''' - ROD is responsible for ensuring that decisions taken on the EGI Operations level are propagated to sites. \n*'''Putting a site in downtime or suspend for urgent matters''' - In general, ROD can place a site in downtime (in the GOC DB) 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 EGI Operations / Operations Support can also suspend a site in the case of an emergency e.g. security incidents or lack of response. \n*'''Notify EGI Operations about core or urgent matters''' - ROD should create tickets to EGI Operations in the case of core or urgent matters.\n\n<br>\n\n== Important to read<br>  ==\n\nBefore you start your duties you should get familiar with following documents:<br> \n\n*[[PROC01 Grid Oversight escalation|Grid Oversight Escalation Procedure]] - this document defines escalation procedure for operational problems. It describes steps and timelines which ROD team should follow. \n*[https://documents.egi.eu/document/301 Dashboard HowTOs and Training Guides] -&nbsp; a collection of HowTOs and guides for EGI Operations. It includes a Dashboard HOWTO, Training Guides which can be used as a presentation for training staff and quick sheets. \n*[[FAQ Regional Operator on Duty|ROD&nbsp;FAQ]] - Frequently Asked Questions related to ROD work<br>\n\n<br> \n\nIt is also important to watch [[Regional Operator on Duty#Video_tutorials|video tutorials ]] prepared for ROD teams. They will walk you through several topics which are important for your work.\n\n== Tools  ==\n\nROD uses several operations tools to perform theirs duties ([http://www.youtube.com/watch?v=bNm4oupAmqI Operations tools video]):<br> \n\n*'''Operations Portal''' - Dashboard tool on the Operations Portal is a main tool which is used by ROD teams. All actions concerning incidents (alarms and tickets) should be performed using this tool. <br> \n*'''The Service Availability Monitoring tool (Nagios)''' - SAM is an official EGI monitoring system based on Nagios. It checks the availability of grid services and creates alarms visible on the Operations Portal dashboard when a service fails.<br> \n*'''GGUS '''- is the EGI&nbsp;central helpdesk system designed for problem reporting and tracking. ROD should not handle operations tickets here. ROD teams should use GGUS to report problems with operations tools and middleware. \n*'''GOC&nbsp;DB '''- is a central database which contains all static information about the grid infrastructure (sites and people)\n\n<br> Links to Operations tools can be found [[Tools|here ]]<br>.\n\n== Contact<br>  ==\n\nEach ROD teams is supposed to provide own mailing list as a contact point to the team. The list of people responsible for ROD in a given NGI and contact points can be found in [https://operations-portal.in2p3.fr/dashboard/regionalPreferences Operations Portal]. \n\nAll ROD mailing list are also subscibed to'''all-central-operator-on-duty''' AT mailman.egi.eu mailing list so to contact other ROD teams you can use this list. \n\nTo contact EGI Operations Support team you can: \n\n*send a GGUS ticket and assign it to EGI Operation Support support unit \n*send an emai to '''operations-support''' AT mailman.egi.eu\n\nYou are welcome to send us questions in case of any doubts concerning ROD duties.<br> \n\n[[Category:Infrastructure_Oversight]]"
                    }
                ]
            }
        }
    }
}