Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "PROC07 Adding new probes to ARGO"

From EGIWiki
Jump to navigation Jump to search
(Created page with '{{Template: Op menubar}} {{Template:Doc_menubar}} Category:Operations Manuals {{TOC_right}} {| border="1" |- | '''Title''' | ''Adding new probes to SAM'' |- | '''Document li…')
 
Line 37: Line 37:
----
----


= Text =
= Overview =


= Text =
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.
 
= Scope =
 
This procedure only applies to probe which are run under OPS VO and its range is global, applies for all Operations Centres in EGI project.
 
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).
 
= Request =
 
* Everyone is allowed to submit the request for adding new probe.
* Applicant is responsible for development and maintenance of Nagios probe.
 
= Procedure =
 
{| border="1" cellspacing="0" cellpadding="5" align="center"
! Step
! Action on
! Action
|-
| 1
| Applicant
| Opens a RT ticket in queue '''requirement'''.
<pre>
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 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)
</pre>
|-
| 2
| JRA1 activity leader
| Schedules presentation of the new probe at the next possible OTAG meeting.
|-
| 3
| Applicant
| Applicant 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
| Applicant
| Applicant opens top level ticket in JIRA system (https://tomtools.cern.ch/jira/secure/) for tracking probe integration process.
|-
| 7
| Applicant, 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
| JRA1 activity leader
| Closes the initial RT ticket.
|}


= Revision History =
= Revision History =
<!-- this section will track changes introduced in the document AFTER it is officially approved by OMB -->
<!-- this section will track changes introduced in the document AFTER it is officially approved by OMB -->

Revision as of 10:36, 11 March 2011

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.

Scope

This procedure only applies to probe which are run under OPS VO and its range is global, applies for all Operations Centres in EGI project.

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).

Request

  • Everyone is allowed to submit the request for adding new probe.
  • Applicant is responsible for development and maintenance of Nagios probe.

Procedure

Step Action on Action
1 Applicant Opens a RT ticket in queue requirement.
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 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 JRA1 activity leader Schedules presentation of the new probe at the next possible OTAG meeting.
3 Applicant Applicant 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 Applicant Applicant opens top level ticket in JIRA system (https://tomtools.cern.ch/jira/secure/) for tracking probe integration process.
7 Applicant, 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 JRA1 activity leader Closes the initial RT ticket.

Revision History