|
|
| (19 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| {{Template:Op menubar}} {{TOC_right}} | | {{Template:Op menubar}} {{TOC_right}} |
| [[Category:Operations]]
| |
| == Introduction ==
| |
|
| |
|
| EGI Operations Start Guide was created to help you<span lang="en" class="short_text" id="result_box"><span class="hps" title="Click for alternate translations"> start with EGI Operations duties. It</span></span> presents the responsibilities of the various parties involved in the running of the EGI infrastructure and guide how to join operations. As a newcomer, you need to understand the structure of the EGI project and roles of operators at different levels. Reading the whole document will give you a complete overall picture of daily operations within EGI.
| | {{DeprecatedAndMovedTo|new_location=https://docs.egi.eu/providers/getting-started/operations_start_guide/}} |
|
| |
|
| == Roles ==
| | [[Category:Operations]] |
| | |
| The following describes the roles that are commonly found in the EGI Infrastructure and Operations. Other terms and definitions can be found in [[Glossary |EGI Glossary]].
| |
| | |
| === '''Site level''' ===
| |
| | |
| ==== Site Administrator ====
| |
| | |
| The person responsible for keeping the site operational. In the scope of Operations, site administrators primarily receive and react on notification of one or more incidents at their site. They will also need to react to security issues that are at a global level, but affect their site. Site administrators should respond to [http://ggus.eu GGUS tickets] in a suitable time frame and be aware of the alarms at their site, eg. through the [https://operations-portal.egi.eu operations dashboard].
| |
| Sites must only operate supported middleware versions. This implies upgrading it from time to time. Emergency releases are treated in a special way. See [[EGI CSIRT:Critical Vulnerability Handling]].
| |
| | |
| All Site management responsibilities are listed in [https://documents.egi.eu/document/31 RC OLA document].
| |
| | |
| ==== Site Operations Manager ====
| |
| | |
| The person responsible for the site at the political and legal level. S/he is responsible for signing the Operations Level Agreement ([https://documents.egi.eu/public/ShowDocument?docid=31 OLA]) between the Site and the NGI that hosts the site operationally. The Site Operations Manager is also responsible for assigning and approving the other site roles in the [https://goc.egi.eu/ GOCDB]. Further, s/he should ensure that administrators are subscribed to relevant mailing lists.
| |
| | |
| ==== Site Security Officer ====
| |
| | |
| The person responsible for keeping the site compliant with the [[EGI CSIRT:Policies|Security policies]]. She/he is also the primary contact for the NGI Security officer and EGI CSIRT. The Site Security Officer deals with security incidents and shall respond to enquiries in a timely fashion as defined in the collection of [[EGI CSIRT:Policies |security procedures and policies]].
| |
| | |
| === '''Regional level''' ===
| |
| | |
| ==== Regional Operator on Duty (ROD) ====
| |
| | |
| A team responsible for solving problems/incidents in the infrastructure according to agreed procedures. ROD (teams) monitor the sites in their region, react to problems identified by the monitoring tools, and oversee problems through to their resolution. They ensure that problems are properly recorded and that the solutions progress according to specified time lines. They also provide support to sites and VOs as needed and provide informational flow to oversight bodies in cases of non-responsive sites. They ensure that all necessary information is available to all parties. The team is provided by each NGI and requires procedural knowledge on the process (rather than technical skills) for their work. New ROD team members are required to read the [[Grid_operations_oversight/ROD_Welcome_page|ROD Welcome page]] and be familiar with [[Grid_operations_oversight/ROD | ROD wiki page]].
| |
| | |
| ==== NGI Security officer ====
| |
| | |
| The member of EGI-CSIRT IRTF (Incidendent Response Task Force) currently on shift. Further information can be found at the [[EGI_CSIRT:IRTF | CSIRT:IRTF]] page. The role of the IRTF team is to handle day to day operational security issues and coordinate Computer-Security-Incident-Response across the EGI infrastructure. NGIs and Sites '''MUST''' respond in a timely manner to its requests and alerts.
| |
| | |
| ==== NGI Manager ====
| |
| | |
| NGI Manager is the contact point for all operational matters and represents the NGI within the [[OMB |OMB board]].
| |
| | |
| S/he is mainly responsible for:
| |
| * keeping the NGI entry in the GOCDB up to date and for managing the status of all sites under that NGI, and ensuring that that information is also kept current
| |
| * addressing problems with Site availability or reliability. The reports are issued on a monthly basis and the NGI manager has 10 days to respond to identified problems
| |
| * attending regular [[OMB |Operations-Management-Board (OMB) meetings]]
| |
| | |
| All NGI management responsibilities are listed in [https://documents.egi.eu/document/463 RP OLA document].
| |
| | |
| === '''Project level''' ===
| |
| | |
| ==== Chief Operations Officer====
| |
| Chief Operations Officer leads EGI Operations, and is responsible for coordinating the operations of the infrastructure across the project.
| |
| | |
| ==== Central Operator on Duty (COD) ====
| |
| | |
| [[Grid_operations_oversight/COD |The Central Operator on Duty (COD)]] team is provided on a global layer and is responsible for the supporting and actively controlling the overall status of Grid services and sites. It coordinates Regional Operator on Duty (ROD) teams and represents the whole ROD structure in terms of technical requirements for operations tools as well as on political level.
| |
| | |
| ==== VO ====
| |
| A Virtual Organisation (VO) is a group of users and, optionally, resources, often not bound to a single institution or national borders, who, by reason of their common membership and in sharing a common goal, are given authority to use a set of resources. Each VO member signs the VO AUP (during registration) which is the policy document describing the goals of the VO thereby defining the expected and acceptable use of the Grid by the users of the VO. User documentation can be found [[User_Documentation |here]].
| |
| | |
| ==== VO manager ====
| |
| | |
| An individual responsible for the membership registry of the VO including its accuracy and integrity.
| |
| | |
| == Joining operations ==
| |
| | |
| In order to join any of the organisational groups in your NGI, you will need to go through the following steps in order:
| |
| | |
| === Obtain a Grid certificate. ===
| |
| | |
| If you do not already have a GRID certificate [http://www.eugridpma.org/members/worldmap/ this page] provides a map of all certification authorities according to country (or NGI). Select your country on the map to find out who is your local CA. Follow the procedure for your local CA to request a certificate. When you have received your certificate, install it into your web browser.
| |
| | |
| CERN provides a webpage for testing your certificate [https://grid-deployment.web.cern.ch/grid-deployment/cgi-bin/CertTest/CertTest.cgi here]. Please use this resource and contact your CA if your certificate does not work.
| |
| | |
| === Join Dteam VO ===
| |
| | |
| It is recommended to join the [[Dteam vo|dteam VO]] at the [https://voms.hellasgrid.gr:8443/vo/dteam/vomrs dteam Registration] page. You should request group membership for <tt>/dteam</tt> and <tt>/dteam/YOUR_NGI</tt>. The dteam group manager will then be notified by the vomrs software.
| |
| | |
| === Request GOCDB access ===
| |
| | |
| * Read [[GOCDB/Input System User Documentation|Input System User Documentation ]] first.
| |
| * Go to the [http://goc.egi.eu/ GOCDB instance]
| |
| ::In the lower left corner there is a ''User status'' box, select ''Register a New Account'' there. In the screen that appears, enter your name, contact information and your DN.
| |
| ::Select ''Manage Roles'' under ''User status'' section and in the next page, select either your NGI or your Site, depending at which level your role is. At the next page, request the role according to [[GOCDB/Input_System_User_Documentation#Roles | role definition]].
| |
| | |
| All new members then '''need to notify their NGI manager''' about their role request, as GOCDB currently '''does not '''send any notification about pending requests.
| |
| | |
| === Register into GGUS ===
| |
| | |
| To register into GGUS please follow the [https://ggus.eu/admin/register.php Central GGUS registration] link. GGUS can be accessed with only your certificate, which is adequate for normal users. However, ROD team members must register and apply for the support role. (The GGUS support staff will approve you quickly as they get the notification automatically.)
| |
| | |
| Some NGIs also have a local helpdesk or a regional GGUS. Ask your NGI manager if how to register to them.
| |
| | |
| === Subscribe to mailing lists. ===
| |
| | |
| NGIs and Sites have local mailing lists for ROD team members and Site Administrators respectively. Please ensure that you subscribe to them. Depending on your role ask your NGI manager or Site manager to have you included on the necessary mailing lists if there is no automatic subscription process.
| |
| | |
| NGI manager should contact operations@egi.eu and state that wish to be subscribed to noc-managers mailing list noc-managers@mailman.egi.eu.
| |
| | |
| | |
| == Documentation ==
| |
| | |
| Documentation relevant to EGI operations can also found at [[Documentation | EGI Documentation wiki page]]
| |
| | |
| == Tools ==
| |
| | |
| A list of tools relevant to EGI operations can also found at [[Tools | EGI Tools wiki page]]
| |
| {| width="100%" style="background: none repeat scroll 0% 0% rgb(249, 249, 249); margin: 1.2em 0px 6px; border: 1px solid rgb(221, 221, 221);"
| |
| |-
| |
| | style="width:61%; color:#000;" |
| |
| {| style="width:280px; border:none; background:none;"
| |
| |-
| |
| | style="width:280px; text-align:center; white-space:nowrap; color:#000;" | <div style="font-size:162%; border:none; margin:0; padding:.1em; color:#000;"><br></div>
| |
| |}
| |
| | |
| | style="width:40%; font-size:95%;" |
| |
| '''Need extra support?'''<br>
| |
| | |
| '''e-mail:''' send an e-mail to operations at mailman.egi.eu
| |
| | |
| '''Ticket:''' submit a ticket to the "Operations" Support Unit in the [http://helpdesk.egi.eu/ EGI Helpdesk]
| |
| | |
| |}
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.