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
(Remove deprecated content)
Tag: Replaced
 
(30 intermediate revisions by 2 users not shown)
Line 2: Line 2:
{{Template:Doc_menubar}}
{{Template:Doc_menubar}}
[[Category:Operations Procedures]]
[[Category:Operations Procedures]]
{{TOC_right}}
[[Category:Deprecated]]
 
{| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;"
 
| style="padding-right: 15px; padding-left: 15px;" |  
{{Ops_procedures
|[[File:Alert.png]] This page is Deprecated; the content has been moved to https://confluence.egi.eu/display/EGIPP/PROC07+Adding+new+probes+to+ARGO
|Doc_title = Adding new probes to SAM
|Doc_link = [[PROC07|https://wiki.egi.eu/wiki/PROC07]]
|Version = 8 June 2016
|Policy_acronym = OMB
|Policy_name = Operations Management Board
|Contact_group = operations@egi.eu
|Doc_status = Approved
|Approval_date = 28 March 2010
|Procedure_statement = This document specifies the procedure for adding new probes to the ARGO-SAM release.
|Owner = Alessandro Paolini
}}
 
= Overview =
 
The purpose of this document is to clearly describe the procedure for adding new [[ARGO#ARGO_tests|Nagios probes]] to the ARGO release.
 
= Definitions  =
 
Please refer to the [[Glossary|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''' are defined in the following way:
*'''Metric''': Metric instances are tuples of flavour, metric name and optionally FQAN. Metric is a synonym for tests used in the development documentation. In operations document "test" is the reference term to be used.
*'''Probe''': a code which implements single or multiple tests.
 
= 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 ARGO 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.
* '''ARGO Product Team'''. The ARGO Product Team is responsible of scheduling, integrating and releasing the accepted probes.
 
= Steps=
 
{| class="wikitable"
! Step
! Action on
! Action
|-
| 1
| Applicant
| A request is submitted through a EGI GGUS ticket (https:/ggus.eu) by assigning to Operations SU.
<pre>
Subject: Request for adding new probe XXX to ARGO-SAM
 
We would like to request adding new probe XXX to ARGO-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)
</pre>
|-
| 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
| ARGO-SAM Product Team
| The SAM Product Team defines schedule for including the new probe into a ARGO-SAM release.
|-
| 6
| Applicant, ARGO-SAM Product Team
| The probe integration process is performed.
|-
| 7
| ARGO-SAM Product Team
| Add the description of the new probe and tests it provides to section "New tests" of the Release notes of ARGO-SAM release which contains the new probe.
|-
| 8
| COO
| Closes the initial GGUS ticket.
|}
 
= Revision History =
 
{| class="wikitable"
|-
! Version !! Authors !! Date !! Comments
|-
|
| M. Krakowian
| 2014-08-19
| Changed contact group -> Operations support
|-
|
| C. Aiftimiei
| 2014-09-18
| Removed broken link "detailed description" on Step 6
|-
|
| Alessandro Paolini
| 2016-06-08
| Changed contact group -> Operations
|-
|
| Alessandro Paolini
| 2017-06-01
| Changed the name SAM to ARGO-SAM
|-
|
| Alessandro Paolini
| 2018-06-19
| Definitions: Metric and Probed as defined in the deprecated [[SAM Tests|terminology page]] (link removed). Overview: updated the link to ARGO/SAM wiki page
|-
|
| Alessandro Paolini
| 2019-12-17
| updating some steps...
|}
|}

Latest revision as of 09:43, 15 April 2022