Difference between revisions of "PROC07 Adding new probes to ARGO"
m (Removed protection from "PROC07 Adding new probes to SAM") |
|
(No difference)
|
Revision as of 10:17, 8 June 2016
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 | Adding new probes to SAM |
Document link | https://wiki.egi.eu/wiki/PROC07 |
Last modified | 18 Sept. 2014 |
Policy Group Acronym | OMB |
Policy Group Name | Operations Management Board |
Contact Group | operations-support@mailman.egi.eu |
Document Status | Approved |
Approved Date | 28 March 2010 |
Procedure Statement | This document specifies the procedure for adding new probes to the SAM release. |
Owner | Owner of procedure |
Overview
The purpose of this document is to clearly describe the procedure for adding new Nagios probes to the SAM release.
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.
The key words Metric, Probe and Test are defined in the SAM Tests terminology page.
Scope
This procedure only applies to probes which are run under OPS VO and whose scope is global. The implication of this is that any change requested through this procedure has an impact on all EGI Operations Centres in EGI.
This procedure does not apply to SAM internal probes which perform monitoring of individual components on the SAM instance (e.g. process monitoring, ActiveMQ connections, etc.).
Entities involved in the procedure
- Applicant. The Applicant submits a request for adding a new probe. Anyone in the operations community - Resource Centre administrators, Operations Centre staff, Resource Infrastructure Operations Managers - is allowed to submit such a request. The Applicant is responsible for the development and maintenance of the proposed Nagios probe. The Nagios probe use case needs to be well documented.
- COO. COO is OMB meeting chair, responsible of processing the request and of accepting/refusing it with the consensus of the Resource Infrastructure Providers.
- SAM Product Team. The SAM Product Team is responsible of scheduling, integrating and releasing the accepted probes.
Steps
Step | Action on | Action |
---|---|---|
1 | Applicant | A request is submitted through a EGI GGUS ticket (https:/ggus.eu) by assigning to Operations SU.
Subject: Request for adding new probe XXX to SAM We would like to request adding new probe XXX to SAM release Prerequisite data: * name of the Nagios probe: * name of service on which the test runs: * link to documentation page: * motivation (which part of the infrastructure will be improved with the new probe or description of users' problems which will be avoided in future - provide list of GGUS tickets is possible) |
2 | COO | Reviews the requirement submitted, and schedules a presentation of the new probe at the next possible OMB meeting. |
3 | Applicant | Presents the new probe. |
4 | OMB | OMB decides if the new probe will be included in the SAM. The next steps are performed only if the probe is accepted. |
5 | SAM Product Team | The SAM Product Team defines schedule for including the new probe into a SAM release. |
6 | Applicant, SAM Product Team | The probe integration process is performed. |
7 | SAM Product Team | Add the description of the new probe and tests it provides to section "New tests" of the Release notes of SAM release which contains the new probe. |
8 | COO | Closes the initial GGUS ticket. |
Revision History
Version | Authors | Date | Comments |
---|---|---|---|
M. Krakowian | 19 August 2014 | Change contact group -> Operations support | |
C. Aiftimiei | 18 Sept. 2014 | Removed broken link "detailed description" on Step 6 |