PROC07 Adding new probes to ARGO

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_Adding_new_probes_to_SAM
Last modified	Tferrari 14:03, 8 March 2011 (UTC)
Policy Group Acronym	OMB
Policy Group Name	Operations Management Board
Contact Person	E. Imamagic
Document Status	DRAFT
Approved Date	specify
Procedure Statement	This document specifies the procedure for adding new probes to the SAM release.

---

Overview

The purpose of this document is to clearly describe the procedure for adding new Nagios probes to SAM release.

Nagios probe is a software component which implements grid service tests. Single Nagios probe can perform one or multiple tests. Detailed description of probes and tests can be found on the SAM Tests page.

Scope

This procedure only applies to probes which are run under OPS VO and whose scope is global, this meaning that the proposed changes are requested to be applicable to 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 adminitrators, Operations Centre staff, Resource Infratstructure 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.
• OTAG Chairman. OTAG is the Operations Tool Advisory Group who is 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.

Procedure

Step	Action on	Action
1	Applicant	A request is submitted through a RT ticket (https://rt.egi.eu/rt/index.html) in queue requirement. A SSO account is needed for this (see Instructions) 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	OTAG chair	Schedules presentation of the new probe at the next possible OTAG meeting.
3	Requester	Presents the new probe.
4	OTAG	OTAG decides if the new probe will be included in the SAM. Remaining steps are performed only if the probe is accepted.
5	SAM team	SAM team defines schedule for including the new probe to SAM.
6	Requester	Requester opens top level ticket in JIRA system (https://tomtools.cern.ch/jira/secure/) for tracking probe integration process.
7	Requester, SAM team	Probe integration process is performed. Detailed description of process is available on the following page: https://tomtools.cern.ch/confluence/display/SAM/Integrating+new+probes+into+SAM.
8	SAM team	Add description of new probe and tests it provides to section "New tests" of Release notes of SAM release which contains the new probe.
9	OTAG chair	Closes the initial RT ticket.