The wiki is in the process of being deprecated and migrated to other supports.

Difference between revisions of "PROC08 Management of the EGI OPS Availability and Reliability Profile"

From EGIWiki
Jump to navigation Jump to search
 
(30 intermediate revisions by 4 users not shown)
Line 2: Line 2:
{{Template:Doc_menubar}}
{{Template:Doc_menubar}}
[[Category:Operations Procedures]]
[[Category:Operations Procedures]]
[[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;" |
|[[File:Alert.png]] This page is '''Deprecated'''; the content has been moved to https://confluence.egi.eu/display/EGIPP/PROC08+Management+of+the+EGI+OPS+Availability+and+Reliability+Profile 
|}
{{TOC_right}}
{{TOC_right}}


Line 7: Line 12:
|Doc_title = Management of the EGI OPS Availability and Reliability Profile
|Doc_title = Management of the EGI OPS Availability and Reliability Profile
|Doc_link = [[PROC08|https://wiki.egi.eu/wiki/PROC08]]
|Doc_link = [[PROC08|https://wiki.egi.eu/wiki/PROC08]]
|Version = 1.0 - 16 March 2011
|Version = 2020-03-02
|Policy_acronym = OMB
|Policy_acronym = OMB
|Policy_name = Operations Management Board
|Policy_name = Operations Management Board
|Contact_group = E. Imamagic
|Contact_group = operations@egi.eu
|Doc_status = Approved  
|Doc_status = Approved  
|Approval_date = 28 March 2011
|Approval_date = 2020-02-20
|Procedure_statement = This document specifies the procedure for modifying the EGI OPS Availability and Reliability profile.
|Procedure_statement = This document specifies the procedure for modifying the EGI OPS Availability and Reliability profile.
}}
|Owner = Alessandro Paolini
}}  


<br>


= Overview =
= Overview =
A change in the profile is needed every time a new Nagios test needs to be added/removed to/from the profile, in order to have its results included/removed in/from Availability and Reliability monthly statistics. A change in the OPS Availability and Reliability profile affects the computation of the monthly Availability and Reliability statistics of all EGI Resource Infrastructures and Resource Centres.
 
A change in the profile is needed every time a new Nagios test needs to be added/removed to/from the profile, in order to have its results included/removed in/from Availability and Reliability monthly statistics. A change in the OPS Availability and Reliability profile affects the computation of the monthly Availability and Reliability statistics of all EGI Resource Infrastructures and Resource Centres.  


= Definitions  =
= Definitions  =


*The key words '''Profile''', '''Metric''', '''Probe''' and '''Test''' are defined in the [[SAM Tests]] page.  
*The key words '''Profile''', '''Metric''', '''Probe''' and '''Test''' are defined in the [https://wiki.egi.eu/wiki/ARGO#ARGO_tests ARGO] page.  
*List of [http://grid-monitoring.cern.ch/myegi/sam-pi/metrics_in_profiles?vo_name=ops&profile_name=ROC_CRITICAL AVAILABILITY tests]
*List of Availability and Reliability tests: [https://poem.egi.eu/poem/admin/poem/profile/2/change/ ARGO_MON_CRITICAL].


Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure.<br>  
Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure.<br>  
Line 29: Line 37:
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 "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.


= Scope =
= Scope =


This procedure is applicable to the EGI OPS Availability and Reliability profile. Any change applied is global, as it has effects on all EGI Resource Centres. The [[External_tools|ACE]] component uses profiles to generate monthly Availability and Reliability reports.
This procedure is applicable to the EGI OPS Availability and Reliability profile. Any change applied is global, as it has effects on all EGI Resource Centres. The ARGO compute engine (CE) uses profiles to generate monthly Availability and Reliability reports.  


This procedure is NOT applicable to VO-specific Availability and Reliability profiles used by non-OPS VOs (e.g. user communities, national operations VOs, etc.).
This procedure is NOT applicable to VO-specific Availability and Reliability profiles used by non-OPS VOs (e.g. user communities, national operations VOs, etc.).  


<!--This procedure does not apply to modifications which have already been agreed with the SAM team:
= Entities involved in the procedure =
* including CREAM-CE probes
* switching from the old SAM CA probe to the new one
* switching from the old SAM ARC probes to Nagios ones.-->


= Entities involved in the procedure =
*'''Applicant'''. The Applicant submits a request for changing the EGI OPS profile. Anybody is allowed to submit the request. The request is submitted to the respective Operations Centre, who after acceptance, forward it to the Operations Management Board [[OMB|OMB]] for discussion.
*'''Operations Centre'''. The entity associated to EGI that is responsible of delivering local operational services to a Resource Infrastructure Provider. In order to contribute resources to EGI a Resource Infrastructure Provider must be associated to an Operations Centre.
*'''Resource Infrastructure Operations Manager'''. Represents the respective Resource Infrastructure within the OMB.
*'''EGI&nbsp;Operations team'''. Team coordinating EGI Infrastructure.
*'''ARGO Team'''. The ARGO Team is responsible of scheduling, integrating and releasing probes.


* '''Applicant'''. The Applicant submits a request for changing the EGI OPS profile. Anybody is allowed to submit the request. The request is submitted to the respective Operations Centre, who after acceptance, forward it to the Operations Management Board [[OMB|OMB]] for discussion.
= Pre-requirements  =
* '''Operations Centre'''. The entity associated to EGI that is responsible of delivering local operational services to a Resource Infrastructure Provider. In order to contribute resources to EGI a Resource Infrastructure Provider must be associated to an Operations Centre.
* '''Resource Infrastructure Operations Manager'''. Represents the respective Resource Infrastructure within the OMB.
* '''Chief Operations Officer''' (COO). COO is the chairman of the Operations Management Board [[OMB|OMB]].
* '''SAM Product Team'''. The SAM Product Team is responsible of scheduling, integrating and releasing probes.


= Pre-requirements =
*This procedure requires usage of the [http://argo.egi.eu ARGO] system for generating monthly availability and reliability statistics. Detailed information about ARGO system can be found on the following link: [http://argoeu.github.io/overview/ http://argoeu.github.io/overview/].
*If the request of change includes the addition of new tests, each test MUST first be integrated with the Operations Dashboard, i.e. being an OPERATIONS test included in the [https://poem.egi.eu/ui/metricprofiles/ARGO_MON_OPERATORS ARGO_MON_OPERATORS] profile is a necessary condition to be included in the [https://poem.egi.eu/ui/metricprofiles/ARGO_MON_CRITICAL ARGO_MON_CRITICAL] profile for A/R computation (see procedure [[PROC06|PROC06]]). This should ensure that the new probe has been tested on the production sites, excluding the occurrence of anomalies not strictly depending on the sites.
*EGI software teams are responsible for the development and testing of new probes.


This procedure requires usage of the [[External_tools|ACE]] system for generating monthly availability and reliability statistics.
= Steps  =
<!-- Detailed information about ACE system can be found on the following link: https://tomtools.cern.ch/confluence/display/SAM/ACE.-->


If the request of change includes the addition of new tests, each test MUST first go through the following steps:
{| class="wikitable"
* integration of the probe in the SAM release (see procedure [[PROC07_Adding_new_probes_to_SAM|PROC07]]);
|-
* integration of the test in the Operations Dashboard (i.e. being an OPERATIONS test is a necessary condition to be an AVAILABILITY test) (see procedure [[PROC06|PROC06]]).
! Step  
The two procedures above assure that the new tests are included in the SAM release, deployed on all Resource Infrastructure SAM instances and accepted by Operations Centre operators.
! Action on  
 
= Steps =
 
{| class="wikitable"
! Step
! Action on
! Action
! Action
|-
|-
| 1
| 1  
| Applicant
| Applicant  
| Sends a change request to the attention of the respective own Operations Centre. The request is submitted through a [https://gus.fzk.de/pages/ticket.php GGUS ticket].  
| Sends a change request to the attention of the respective own Operations Centre. The request is submitted through a [https://gus.fzk.de/pages/ticket.php GGUS ticket].  
Use the "Affected ROC/NGI" to address the ticket to the appropriate Operations Centre.
Use the "Affected ROC/NGI" to address the ticket to the appropriate Operations Centre. Template:  
Template:
<pre>Subject: Request for adding/removing XXX(,YYY,...) test(s) to/from the EGI OPS A/R Profile
<pre>
Subject: Request for adding/removing XXX(,YYY,...) test(s) to/from the EGI OPS A/R Profile


We would like to request adding/removing XXX(,YYY,...) test(s) to/from from the EGI OPS Profile
We would like to request adding/removing XXX(,YYY,...) test(s) to/from from the EGI OPS Profile


Prerequisite data:
Prerequisite data:
* name of SAM test(s):
* name of ARGO test(s):
* name of service on which the test runs:
* name of service on which the test runs:
* link to documentation page:
* link to documentation page:
Line 84: Line 82:
</pre>
</pre>
|-
|-
| 2
| 2  
| Operations Centre
| Operations Centre  
| The Operations Centre process the request specified in the GGUS ticket for acceptance/rejection.  
| The Operations Centre process the request specified in the GGUS ticket for acceptance/rejection.  
Motivations for rejection need to specify in the GGUS ticket.  
Motivations for rejection need to specify in the GGUS ticket.  
In case of acceptance, a [https://rt.egi.eu/rt/index.html RT ticket] is opened in queue '''noc-managers''' to forward the request for discussion in the OMB.  
 
Template:
In case of acceptance, a GGUS ticket is opened to EGI Operations Support Unit to forward the request for discussion in the OMB. Template:  
<pre>
<pre>Subject: Request for adding/removing XXX(,YYY,...) test(s) to/from the EGI OPS Profile
Subject: Request for adding/removing XXX(,YYY,...) test(s) to/from the EGI OPS Profile


We would like to request adding/removing XXX(,YYY,...) test(s) to/from the EGI OPS Profile.  
We would like to request adding/removing XXX(,YYY,...) test(s) to/from the EGI OPS Profile.  
Line 97: Line 94:
</pre>
</pre>
|-
|-
| 3
| 3  
| COO and Resource Infrastructure Operations Manager
| EGI Opertions team&nbsp; and Resource Infrastructure Operations Manager  
| COO schedules a presentation of the change requested at the next possible OMB meeting. The relevant Resource Infrastructure Operations Manager presents the request during the meeting. The Applicant is invited to attend the meeting. Only one request will be processed at a time as the impact of a change needs to be assessed. Requests are processed depending on their priority, as agreed by the [[OMB|OMB]].
| EGI Opertions team schedules a presentation of the change requested at the next possible OMB meeting. The relevant Resource Infrastructure Operations Manager presents the request during the meeting. The Applicant is invited to attend the meeting. Only one request will be processed at a time as the impact of a change needs to be assessed. Requests are processed depending on their priority, as agreed by the [[OMB|OMB]].
|-
| 4 (*)
| COO
| Opens a GGUS ticket requesting the creation of a new ACE profile with a modified set of AVAILABILITY tests to the SAM/Nagios 3rd level SU.
|-
|-
| 5 (*)
|
| ACE team
| EGI Opertions team  
| ACE team creates the new ACE profile.
| Opens a GGUS ticket to "Monitoring (ARGO)" requesting the addition (or removal) to the ARGO_MON_CRITICAL profile.  
|-
|-
| 6
| 5
| SA1.8 staff
| ARGO team
| For the following '''one month''' two availability and reliability reports are generated. SA1.8 staff compares the figures and presents them at the next OMB meeting with a recommendation for acceptance or rejection.
| Implements the change on the agreed date (generally, the first day of the month).
|-
|-
| 7
| 6
| OMB
| EGI Opertions team
| If the availability and reliability statistics generated with the new profile are satisfactory, OMB approves the modification.
| Before closing the ticket, verifies there are no anomalies with the new A/R reports and report back to the NGI Managers by email or to the next OMB meeting.
|-
|-
| 8 (*)
| 7
| COO
| EGI Opertions team
| Opens a child GGUS ticket requesting that the new availability and reliability profile becomes the official for EGI.
| Broadcasts the modification to all relevant parties (i.e. Operations Centres and Resource Centres) through the next Monthly Broadcast. Closes the GGUS ticket&nbsp;
|-
| 9
| COO
| Broadcasts the modification to all relevant parties (i.e. Operations Centres and Resource Centres). Closes the GGUS ticket (parent and child).
|}
|}


(*) - These steps depend on the procedure for creating new profiles which will be defined by the ACE team once the ACE is in production. Steps defined here have been provided by the ACE team. This procedure will be updated if any change occurs.
= Revision History  =


= Revision History =
{| class="wikitable"
{| class="wikitable"
|-
|-
! Version !! Authors !! Date !! Comments
! Version  
! Authors  
! Date  
! Comments
|-
| <br>
| T. Ferrari
| 18/10/2011
| removed obsolete information: "This procedure does not apply to modifications which have already been agreed with the SAM team: including CREAM-CE probes, switching from the old SAM CA probe to the new one, switching from the old SAM ARC probes to Nagios ones."
|-
| <br>
| M. Krakowian
| 19 August 2014
| Change contact group -&gt; Operations support
|-
| <br>
| P. Daoglou and P. Korosoglou
| 30 September 2015
| Updates in procedure. Replacement of ACE references with ARGO.
|-
|
| Alessandro Paolini
| 2016-06-08
| Change contact group -&gt; Operations
|-
|-
|  
|  
| T. Ferrari
| Alessandro Paolini
| 18/10/2011
| 2019-12-17
| removed obsolete information: "This procedure does not apply to modifications which have already been agreed with the SAM team: including CREAM-CE probes, switching from the old SAM CA probe to the new one, switching from the old SAM ARC probes to Nagios ones."
| updating some old links and names; updating some steps (it seems it is no more necessary creating a "testing" A/R report before approving the changes)
|}
|}
[[Category:Operations_Procedures]]

Latest revision as of 14:37, 4 August 2021

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
Alert.png This page is Deprecated; the content has been moved to https://confluence.egi.eu/display/EGIPP/PROC08+Management+of+the+EGI+OPS+Availability+and+Reliability+Profile


Title Management of the EGI OPS Availability and Reliability Profile
Document link https://wiki.egi.eu/wiki/PROC08
Last modified 2020-03-02
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations@egi.eu
Document Status Approved
Approved Date 2020-02-20
Procedure Statement This document specifies the procedure for modifying the EGI OPS Availability and Reliability profile.
Owner Alessandro Paolini



Overview

A change in the profile is needed every time a new Nagios test needs to be added/removed to/from the profile, in order to have its results included/removed in/from Availability and Reliability monthly statistics. A change in the OPS Availability and Reliability profile affects the computation of the monthly Availability and Reliability statistics of all EGI Resource Infrastructures and Resource Centres.

Definitions

  • The key words Profile, Metric, Probe and Test are defined in the ARGO page.
  • List of Availability and Reliability tests: ARGO_MON_CRITICAL.

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.

Scope

This procedure is applicable to the EGI OPS Availability and Reliability profile. Any change applied is global, as it has effects on all EGI Resource Centres. The ARGO compute engine (CE) uses profiles to generate monthly Availability and Reliability reports.

This procedure is NOT applicable to VO-specific Availability and Reliability profiles used by non-OPS VOs (e.g. user communities, national operations VOs, etc.).

Entities involved in the procedure

  • Applicant. The Applicant submits a request for changing the EGI OPS profile. Anybody is allowed to submit the request. The request is submitted to the respective Operations Centre, who after acceptance, forward it to the Operations Management Board OMB for discussion.
  • Operations Centre. The entity associated to EGI that is responsible of delivering local operational services to a Resource Infrastructure Provider. In order to contribute resources to EGI a Resource Infrastructure Provider must be associated to an Operations Centre.
  • Resource Infrastructure Operations Manager. Represents the respective Resource Infrastructure within the OMB.
  • EGI Operations team. Team coordinating EGI Infrastructure.
  • ARGO Team. The ARGO Team is responsible of scheduling, integrating and releasing probes.

Pre-requirements

  • This procedure requires usage of the ARGO system for generating monthly availability and reliability statistics. Detailed information about ARGO system can be found on the following link: http://argoeu.github.io/overview/.
  • If the request of change includes the addition of new tests, each test MUST first be integrated with the Operations Dashboard, i.e. being an OPERATIONS test included in the ARGO_MON_OPERATORS profile is a necessary condition to be included in the ARGO_MON_CRITICAL profile for A/R computation (see procedure PROC06). This should ensure that the new probe has been tested on the production sites, excluding the occurrence of anomalies not strictly depending on the sites.
  • EGI software teams are responsible for the development and testing of new probes.

Steps

Step Action on Action
1 Applicant Sends a change request to the attention of the respective own Operations Centre. The request is submitted through a GGUS ticket.

Use the "Affected ROC/NGI" to address the ticket to the appropriate Operations Centre. Template:

Subject: Request for adding/removing XXX(,YYY,...) test(s) to/from the EGI OPS A/R Profile

We would like to request adding/removing XXX(,YYY,...) test(s) to/from from the EGI OPS Profile

Prerequisite data:
* name of ARGO test(s):
* name of service on which the test runs:
* link to documentation page:
* motivation (which part of the infrastructure will be improved with the new test
 or description of users' problems which will be avoided in future - provide list
 of GGUS tickets is possible)
2 Operations Centre The Operations Centre process the request specified in the GGUS ticket for acceptance/rejection.

Motivations for rejection need to specify in the GGUS ticket.

In case of acceptance, a GGUS ticket is opened to EGI Operations Support Unit to forward the request for discussion in the OMB. Template:

Subject: Request for adding/removing XXX(,YYY,...) test(s) to/from the EGI OPS Profile

We would like to request adding/removing XXX(,YYY,...) test(s) to/from the EGI OPS Profile. 
Please see details in GGUS ticket _link to Applicant's GGUS ticket_.
3 EGI Opertions team  and Resource Infrastructure Operations Manager EGI Opertions team schedules a presentation of the change requested at the next possible OMB meeting. The relevant Resource Infrastructure Operations Manager presents the request during the meeting. The Applicant is invited to attend the meeting. Only one request will be processed at a time as the impact of a change needs to be assessed. Requests are processed depending on their priority, as agreed by the OMB.
4 EGI Opertions team Opens a GGUS ticket to "Monitoring (ARGO)" requesting the addition (or removal) to the ARGO_MON_CRITICAL profile.
5 ARGO team Implements the change on the agreed date (generally, the first day of the month).
6 EGI Opertions team Before closing the ticket, verifies there are no anomalies with the new A/R reports and report back to the NGI Managers by email or to the next OMB meeting.
7 EGI Opertions team Broadcasts the modification to all relevant parties (i.e. Operations Centres and Resource Centres) through the next Monthly Broadcast. Closes the GGUS ticket 

Revision History

Version Authors Date Comments

T. Ferrari 18/10/2011 removed obsolete information: "This procedure does not apply to modifications which have already been agreed with the SAM team: including CREAM-CE probes, switching from the old SAM CA probe to the new one, switching from the old SAM ARC probes to Nagios ones."

M. Krakowian 19 August 2014 Change contact group -> Operations support

P. Daoglou and P. Korosoglou 30 September 2015 Updates in procedure. Replacement of ACE references with ARGO.
Alessandro Paolini 2016-06-08 Change contact group -> Operations
Alessandro Paolini 2019-12-17 updating some old links and names; updating some steps (it seems it is no more necessary creating a "testing" A/R report before approving the changes)