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 "PROC10 Recomputation of SAM results or availability reliability statistics"

From EGIWiki
Jump to navigation Jump to search
Line 2: Line 2:


{{Ops_procedures
{{Ops_procedures
|Doc_title = Recomputation of SAM results and/or availability/reliability statistics
|Doc_title = Recomputation of availability/reliability statistics
|Doc_link = [[PROC10|https://wiki.egi.eu/wiki/PROC10]]
|Doc_link = [[PROC10|https://wiki.egi.eu/wiki/PROC10]]
|Version = 3.11.2014
|Version = 28.09.2015
|Policy_acronym = OMB
|Policy_acronym = OMB
|Policy_name = Operations Management Board
|Policy_name = Operations Management Board
|Contact_group = operations-support@mailman.egi.eu
|Contact_group = operations-support@mailman.egi.eu
|Doc_status = Approved
|Doc_status = Approved
|Approval_date = 26 March 2012
|Approval_date = 29.10.2015
|Procedure_statement = This procedure documents the steps for requesting a correction in the SAM test results and in the related availability/reliability statistics.
|Procedure_statement = This procedure documents the steps for requesting a correction in the SAM test results and in the related availability/reliability statistics.
}}  
}}  
Line 17: Line 17:
= Overview  =
= Overview  =


This procedure documents the steps for requesting a correction in the OPS VO [[SAM Instances|SAM test results]] and in the related [[Availability and reliability monthly statistics|availability/reliability statistics]] if applicable. <!--A recomputation of these statistics for the affected month is not needed if test results are notified and corrected before the statistics of that month are computed and distributed. Problems with the SAM results should be notified as soon as possible once detected, in order to allow sufficient time for fixing of these and thus to avoid that monthly availability/reliability statistics for the affected month have to be re-computed.-->
This procedure documents the steps for requesting a correction in the OPS VO [https://wiki.egi.eu/wiki/SAM_Instances SAM&nbsp;test results] and in the related [https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_statistics availability/reliability statistics] if applicable.  
 
Figures are available trough the web interface&nbsp;: http://argo.egi.eu


DISCLAIMER: This procedure is only applicable to EGI OPS test results. Procedures for the computation of VO-specific availability report are VO-specific and are out of this scope.  
DISCLAIMER: This procedure is only applicable to EGI OPS test results. Procedures for the computation of VO-specific availability report are VO-specific and are out of this scope.  
Line 36: Line 38:
= Re-computation policy  =
= Re-computation policy  =


Starting from the 01 May 2012 monitoring '''results can be recomputed only in the case of problems with the monitoring infrastructure itself. '''<br>
Starting from the 01 May 2012:


'''No re-computations will be performed in case of issues with the deployed middleware '''(e.g. in case of documented bugs affecting the availability of a production service end-point), which will be consequently reflected in lower availability/reliability.  
*monitoring '''results can be recomputed only in the case of problems with the monitoring infrastructure itself. '''<br>
*'''No re-computations will be performed in case of issues with the deployed middleware '''(e.g. in case of documented bugs affecting the availability of a production service end-point), which will be consequently reflected in lower availability/reliability.


<br>  
<br>  
Line 49: Line 52:
<br>  
<br>  


'''The deadline for requesting re-computations is 10 calendar days after the publication and announcement of the monthly Availability/Reliability reports for a given month X (typically the announcement will be distributed on the 1st day of month X+1).''' <br>  
'''The deadline: '''10 calendar days after the publication and announcement of the monthly Availability/Reliability reports for a given month X (typically the announcement will be distributed on the 1st day of month X+1). <br>  


According to the re-computation requests received, A/R reports will be regenerated only once for each month, after the 10th of month X+1.  
According to the re-computation requests received, A/R reports will be regenerated only once for each month, after the 10th of month X+1.  


= How to request a re-computation of OPS monitoring results  =
= How to request a re-computation of OPS monitoring results  =
== The request is originated by a Resource Centre  ==
<br>


{| class="wikitable"
{| class="wikitable"
Line 66: Line 65:
|-
|-
| 1  
| 1  
| Resource Centre
| Site administrator / ROD team
|  
|  
As soon as the problem is detected, notify your NGI operations centre by opening a [http://helpdesk.egi.eu/ GGUS ticket].
As soon as the problem is detected, please fill this form&nbsp;: [http://argo.egi.eu/lavoisier/recomputation http://argo.egi.eu/lavoisier/recomputation] and indicate<br>


Please address the ticket to your Operations Centre support unit, who is responsible of validating the request. In the GGUS ticket you must mention:
#Your name and email
#the site(s) affectected by the problem
#a description of the problem
#the profile affected
#the starting and ending time of the problem (including day and hour in UTC)<br>


#the starting and ending time of the problem (including day and hour in UTC)
The submission of the form will inform the ARGO / EGI Operations team and your request will be in pending status.
#the Site, NGI/federation of NGIs affected by the problem
#the VO affected by the problem (must be the OPS VO)
#a description of the problem<br>


|-
|-
| 2  
| 2  
| Opertions Centre
| ARGO&nbsp;team / EGI Operations team
|  
|  
The NGI operations centre validates the request.  
Member of the staff validates the request. <br>


Note:''&nbsp;It is recommended to open a [[PROC10|ticket for recomputation ]]as soon as the problems has been detected.''
You will be informed about the confirmation / rejection of the request by email .  


|-
|-
| 3  
| 3  
| Opertions Centre
| ARGO&nbsp;team / EGI Operations team
|  
|  
If the request is deemed valid, a GGUS ticket is sent to [[GGUS:SLM-FAQ|Service Level Management]](SLM) Support Unit.  
If the request is accepted - the recomputation will be triggered as soon as possible .  


The SLM support team will take care of discussing all requests received with the SAM team.
The status of the recomputation will be visible trough a web page (link given in the email of the previous step )


|-
| 4
| SLM SU
|
#validating the reported problems
#discuss the reported problems with the SAM Support Unit if needed
#notify the SAM SU about the requests received through a new parent ticket is submitted to SAM with the children tickets of the validated requests
|-
| 5<br>
| SLM SU
|
#The SAM Support Unit is responsible of checking the requests and of regenerating the results. For the accepted requests all Nagios metric results for any site and service are set to ''unknown'' status from the beginning of the hour reported in the starting time to one hour after the ending time. This is to cover late results that could have arrived later. the availability and reliability of other sites won't be affected, as unknown periods are not considered in the computation.
#New monthly availability statistics will be recomputed for that particular period, Site, NGI/federation of NGIs.
#A new report will be made available 10 days after the first publication of the report.
#After publication of the new report, all child GGUS tickets will be closed.
|-
| 6
| SLM SU
| Close the parent ticket.
|}
|}


<br>
<br>  
 
== The request is originated by an NGI/EIRO operations centre  ==
 
Follow the procedure defined in the section above, starting from STEP 3. <!-- # '''STEP 3''': if the request for recomputation of the test results is accepted, the SAM Support Unit will be responsible of fixing the results and of triggering a recomputation of the monthly availability statistics if necessary. The following these steps are followed:
## All Nagios metric results for any site and service are set to ''unknown'' status from the beginning of the hour reported in the starting time to one hour after the ending time. This is to cover late results that could have arrived later.
## Availability/reliability are then recomputed for that particular period, Site, NGI/federation of NGIs if necessary. As a consequence, the availability and reliability of other sites won't be affected, as unknown periods are not considered in the computation.
# '''STEP 4''': in case new availability/reliability statistics are computed, when these are ready for distribution, the SAM/Nagios SU reassigns the ticket to the SLM Support Unit, in order to notify that a new set of reports can be re-distributed to EGI.-->
 
= External links  =
 
*[https://tomtools.cern.ch/confluence/display/SAMDOC/Availability+Re-computation+Policy WLCG Availability re-computation policy]


= Tips  =
= Tips  =
Line 175: Line 143:
|-
|-
|  
|  
| M. Krakowian
| M. Krakowian  
| 3.11.2014
| 3.11.2014  
| Add step2: Note:''&nbsp;It is recommended to open a [https://wiki.egi.eu/wiki/PROC10 ticket for recomputation as] soon as the problems has been detected.''
|  
Add step2: Note:''&nbsp;It is recommended to open a [https://wiki.egi.eu/wiki/PROC10 ticket for recomputation as] soon as the problems has been detected.''  
 
|-
|
| C. L'Orphelin
| 28.09.2015
| ARGO&nbsp;procedure&nbsp;: no need of a ticket , replacement by a recomputation form
|}
|}


[[Category:Operations_Procedures]]
[[Category:Operations_Procedures]]

Revision as of 15:15, 6 November 2015

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 Recomputation of availability/reliability statistics
Document link https://wiki.egi.eu/wiki/PROC10
Last modified 28.09.2015
Policy Group Acronym OMB
Policy Group Name Operations Management Board
Contact Group operations-support@mailman.egi.eu
Document Status Approved
Approved Date 29.10.2015
Procedure Statement This procedure documents the steps for requesting a correction in the SAM test results and in the related availability/reliability statistics.
Owner Owner of procedure



Overview

This procedure documents the steps for requesting a correction in the OPS VO SAM test results and in the related availability/reliability statistics if applicable.

Figures are available trough the web interface : http://argo.egi.eu

DISCLAIMER: This procedure is only applicable to EGI OPS test results. Procedures for the computation of VO-specific availability report are VO-specific and are out of this scope.

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.

Who can submit a request?

Re-computations can be requested by:

  • site administrators
  • regional operations staff.

Re-computation policy

Starting from the 01 May 2012:

  • monitoring results can be recomputed only in the case of problems with the monitoring infrastructure itself.
  • No re-computations will be performed in case of issues with the deployed middleware (e.g. in case of documented bugs affecting the availability of a production service end-point), which will be consequently reflected in lower availability/reliability.


Some examples of possible issues justifying a re-computation request:

  • invalid proxy certificate used for submitting the monitoring probes in a Nagios instance;
  • problems with the Storage Element used for replica management tests resulting in errors on CE's metrics.


The deadline: 10 calendar days after the publication and announcement of the monthly Availability/Reliability reports for a given month X (typically the announcement will be distributed on the 1st day of month X+1).

According to the re-computation requests received, A/R reports will be regenerated only once for each month, after the 10th of month X+1.

How to request a re-computation of OPS monitoring results

Step Action on Action
1 Site administrator / ROD team

As soon as the problem is detected, please fill this form : http://argo.egi.eu/lavoisier/recomputation and indicate

  1. Your name and email
  2. the site(s) affectected by the problem
  3. a description of the problem
  4. the profile affected
  5. the starting and ending time of the problem (including day and hour in UTC)

The submission of the form will inform the ARGO / EGI Operations team and your request will be in pending status.

2 ARGO team / EGI Operations team

Member of the staff validates the request.

You will be informed about the confirmation / rejection of the request by email .

3 ARGO team / EGI Operations team

If the request is accepted - the recomputation will be triggered as soon as possible .

The status of the recomputation will be visible trough a web page (link given in the email of the previous step )


Tips

  • Date formats

You can use the Unix date command to convert the start and end time from your time zone to UTC using the ISO 8601 format.

the start time must be rounded to the lower hour and the end time rounded to the higher hour

Example: 

# date --date="12 Feb 2012 17:00 CET" --utc --iso-8601=hours

will give: 

2012-02-12T16:00+0000

Revision history

Version Authors Date Comments

George Fergadis/AUTH 03/05/2012 updated policy and procedure to reflect the OMB decision of the March 2012 meeting

George Fergadis/AUTH 17/01/2012 the text of the procedure is fixed to clarify that both RC administrators and regional operations staff can request a re-computation.

George Fergadis/AUTH 16/01/2012 the text of the procedure is fixed to clarify that the recomputation of test results can be requested before the end of the affected month, in which case if sufficient time is allowed for fixing of the test results, no re-computation of availability/reliability statistics will be needed.

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

Add step2: Note: It is recommended to open a ticket for recomputation as soon as the problems has been detected.

C. L'Orphelin 28.09.2015 ARGO procedure : no need of a ticket , replacement by a recomputation form
Retrieved from "https://wiki.egi.eu/w/index.php?title=PROC10_Recomputation_of_SAM_results_or_availability_reliability_statistics&oldid=84611"