Difference between revisions of "PROC05 Validation of Operations Centre Nagios"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
{{Template:Op menubar}} | {{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} | ||
{{Template:Doc_menubar}} | |||
{{TOC_right}} | |||
{{Ops_procedures | {{Ops_procedures | ||
Line 13: | Line 10: | ||
|Doc_status = Approved | |Doc_status = Approved | ||
|Approval_date = 10 August 2010 | |Approval_date = 10 August 2010 | ||
|Procedure_statement = The purpose of this document is to define validation procedure of | |Procedure_statement = The purpose of this document is to define validation procedure of Operations Centre Nagios | ||
}} | }} | ||
= Overview = | |||
Validation | The document describes the process of how to register and validate Operations Centre Nagios instance. | ||
* instance must pass all tests on ops-monitor instance | |||
* all internal tests (assigned to nagios server) must be OK | = Definitions = | ||
* ROD must check status of services and they shouldn't see any errors that cannot be justified with actual site error. | |||
* all this should run for at least 7 days so that we can see that local MyEGI data is fine | 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.<br> | |||
== Registration Steps == | |||
*add it to GOCDB and to service group NGI_XX_SERVICES | |||
*open ticket for SAM/Nagios to add it to http://gridops.cern.ch/config/nagios-roles.conf | |||
*open ticket for Operations Portal guys to enable receiving alarms from it | |||
== Validation Steps == | |||
*instance must pass all tests on ops-monitor instance | |||
*all internal tests (assigned to nagios server) must be OK | |||
*ROD must check status of services and they shouldn't see any errors that cannot be justified with actual site error. | |||
*all this should run for at least 7 days so that we can see that local MyEGI data is fine | |||
[[Category:Operations_Procedures]] |
Revision as of 14:45, 21 May 2013
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
Title | Validation of a Operations Centre Nagios |
Document link | https://wiki.egi.eu/wiki/PROC05 |
Last modified | 1.0 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | Emir Imamagic |
Document Status | Approved |
Approved Date | 10 August 2010 |
Procedure Statement | The purpose of this document is to define validation procedure of Operations Centre Nagios |
Owner | Owner of procedure |
Overview
The document describes the process of how to register and validate Operations Centre Nagios instance.
Definitions
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
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.
Registration Steps
- add it to GOCDB and to service group NGI_XX_SERVICES
- open ticket for SAM/Nagios to add it to http://gridops.cern.ch/config/nagios-roles.conf
- open ticket for Operations Portal guys to enable receiving alarms from it
Validation Steps
- instance must pass all tests on ops-monitor instance
- all internal tests (assigned to nagios server) must be OK
- ROD must check status of services and they shouldn't see any errors that cannot be justified with actual site error.
- all this should run for at least 7 days so that we can see that local MyEGI data is fine