|
|
| (19 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| {{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} | | {{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} |
| | | [[Category:Deprecated]] |
| <br> {{Ops_procedures
| | {| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;" |
| |Doc_title = Setting Nagios test status to operations
| | | style="padding-right: 15px; padding-left: 15px;" | |
| |Doc_link = [[PROC06 |https://wiki.egi.eu/wiki/PROC06]]
| | |[[File:Alert.png]] This page is '''Deprecated'''; the content has been moved to https://confluence.egi.eu/display/EGIPP/PROC06+Setting+Nagios+test+status+to+operations |
| |Version = 19 August 2014 | |
| |Policy_acronym = OMB | |
| |Policy_name = Operations Management Board
| |
| |Contact_group = operations-support@mailman.egi.eu
| |
| |Doc_status = Approved | |
| |Approval_date = 23.11.2010 | |
| |Procedure_statement = The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for setting Nagios tests an operations test. A Nagios test is set as operations test to enable the operations dashboard to display an alarm in case the test fails.
| |
| }}
| |
| | |
| = Overview =
| |
| | |
| The purpose of this document is to clearly describe the actions and the relative steps to be undertaken for setting Nagios tests an operations test. A Nagios test is set as operations test to enable the operations dashboard to display an alarm in case the test fails.
| |
| | |
| '''This procedure only applies for tests run under OPS VO and its range is global, applies for all Operations Centres in EGI project.''' | |
| | |
| | |
| = Definitions =
| |
| | |
| Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure.<br>
| |
| | |
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
| |
| | |
| | |
| | |
| = Steps =
| |
| | |
| == Prerequisites ==
| |
| | |
| The SAM test needs to meet the following requirements.
| |
| | |
| #It satisfies quality criteria in agreement with the UMD operational capabilities quality criteria: https://documents.egi.eu/document/240.
| |
| #It is properly documented.
| |
| #It must be part of an official nagios release.
| |
| #It must have been deployed in production for at least one month without problems.
| |
| #It must be available for validation by Operations
| |
| | |
| == Sending a request ==
| |
| | |
| *Anybody is can submit the request for making the test an operations test.
| |
| *The request should be submitted to Operations via a GGUS ticket.
| |
| | |
| == Validation ==
| |
| | |
| The general idea is that tickets specified in the table below must be closed before being able to move on to the next step in the procedure.
| |
| | |
| {| class="wikitable"
| |
| |-
| |
| ! Step
| |
| ! Action on
| |
| ! Action
| |
| |-
| |
| | 1
| |
| | Applicant
| |
| | Opens a [https://ggus.eu/ GGUS] ticket to Operations to start the process. <pre>Subject: Request for setting XXX test an operations test
| |
| | |
| Dear Operations,
| |
| | |
| We would like to request for setting XXX test an operations test
| |
| | |
| Prerequisite data:
| |
| * name of nagios probe:
| |
| * name of service on which the test runs:
| |
| * link to documentation page:
| |
| * motivation (which part of the infrastructure will be improved by making XXX test
| |
| or description of users' problems which will be avoided in future - provide list | |
| of GGUS tickets is possible)
| |
| | |
| Best Regards
| |
| XXX
| |
| </pre>
| |
| |-
| |
| | 2
| |
| | Operations
| |
| | Checks the status of the Nagios probe to see if it meets the specified quality criteria.
| |
| |-
| |
| | 3
| |
| | Operations
| |
| | Operations contacts the OMB to request the approval of the new operations test. Date is specified (at least 1 month in future)
| |
| |-
| |
| | 4
| |
| | NGIs
| |
| | Request to the ROD teams to try making the test OK. 75% OK in total (entire EGI) is understood as threshold for passing to the next step. If not possible to proceed, report problems to OMB.
| |
| |-
| |
| | 5
| |
| | Operations support
| |
| | The announcement about the new operations test is Monthly broadcast
| |
| (This broadcast should be sent to site managers, NOC/ROC managers and ROD teams) See the template below for an indication of the message content.
| |
| <pre>Subject: XXX have been added to the EGI Operations Profile on XXX
| |
| | |
| Dear All,
| |
| | |
| We would like to announce that test XXX will become operational on XXX
| |
| | |
| Short description of the test:
| |
| | |
| The documentation can be found:
| |
| | |
| Best regards,
| |
| </pre>
| |
| |-
| |
| | 6
| |
| | Operations
| |
| | Mark the test as operations test in the Operational Portal.
| |
| |-
| |
| | 7
| |
| | SAM
| |
| | Add new test into ROC_OPERATORS profile in MyEGI<br> if the test if run by regional Nagios instances.
| |
| |-
| |
| | 8
| |
| | Operations
| |
| | Final check. Close parent ticket
| |
| |} | | |} |
|
| |
| <br>
| |
|
| |
| = Revision history =
| |
|
| |
| {| class="wikitable"
| |
| |-
| |
| ! Version
| |
| ! Authors
| |
| ! Date
| |
| ! Comments
| |
| |-
| |
| |
| |
| | M. Krakowian
| |
| | 19 August 2014
| |
| | Change contact group -> Operations support
| |
| |}
| |
|
| |
| [[Category:Operations_Procedures]]
| |
The wiki is deprecated and due to be decommissioned by the end of September 2022.