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 "PROC04 Quality verification of monthly availability and reliability statistics"

From EGIWiki
Jump to navigation Jump to search
(Remove deprecated content)
Tag: Replaced
 
(29 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Template:Op menubar}} {{Template:Doc_menubar}} {{TOC_right}} {{Ops_procedures
{{Template:Op menubar}} {{Template:Doc_menubar}}  
|Doc_title = Quality verification of monthly availability and reliability statistcs
[[Category:Deprecated]]
|Doc_link = https://wiki.egi.eu/wiki/PROC04
{| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;"
|Version = 2.0
| style="padding-right: 15px; padding-left: 15px;" |  
|Policy_acronym = OMB
|[[File:Alert.png]] This page is '''Deprecated'''; the content has been moved to https://confluence.egi.eu/display/EGIPP/PROC04+Quality+verification+of+monthly+availability+and+reliability+statistics 
|Policy_name = Operations Management Board
|Contact_group =  operations at mailman.egi.eu
|Doc_status = Approved
|Approval_date = 30 October 2012
|Procedure_statement = Instructions RODs and Operations Centres on how to handle justification for poor monthly performance
}}
 
= Overview  =
 
The document describes the process of how to handle justification for poor monthly performance.
 
Links to all monthly statistics are provided on a regular basis at [https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_statistics Availability and reliability monthly statistics page].
 
= Definitions  =
 
Please refer to the [[Glossary|EGI Glossary]] for the definitions of the terms used in this procedure.<br>
 
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.<br>
 
= Process of handling RC Availability and Reliability  =
 
Availability alarms are raised on [https://operations-portal.egi.eu/dashboard Operations Dashboard] and are thought to be a warning for NGI informing about poor performance of site within the last 30 days.
 
== Entities involved in the procedure  ==
 
'''Regional Operator on Duty (ROD)''': team provided by NGIs and responsible for handling RC&nbsp;availability and reliability alarms through Dashboard in Operations Portal. <br>
 
'''Central Operator on Duty (COD)''': team provided by EGI and responsible for handling of underperforming sites which were below the target for 3 consecutive months.
 
'''NGI&nbsp;manager:'''&nbsp;person who suspend the underperforming site or provide site justification.
 
== Steps  ==
 
When an alarm is raised, it means that the Availability metric has dropped below the threshold of 70% for the last 30 days period.
 
'''Handling alarms:'''<br>
 
{| class="wikitable"
|-
! Step#
! Responsible
! Action
|- valign="top"
| 1
| ROD
| Creates a ticket through the dashboard informing site administrator that the Availability metric has dropped below the threshold of 70% for the last 30 days period.
|- valign="top"
| 2
| ROD
| Escalation of the ticket will vary between NGIs. NGIs have freedom to decide if they want to apply own escalation procedure or treat avaliability tickets just as an information for site administrators.
|- valign="top"
| 3
| ROD
|
*Ticket can be closed as soon as the alarm goes into OK status (however it is recommended to make sure it is a couple percent above the threshold before closing it. e.g. 80%).
*If the problem continues for over 30 days the ticket should be closed otherwise ticket will appear on COD dashboard and affect ROD performance index.
|}
|}
'''Handling of underperforming sites (below the target for 3 consecutive months):'''
{| class="wikitable"
|-
! Step#
! Responsible
! Action
|- valign="top"
| 1
| COD
| Creates a GGUS ticket for each underperforming site.
|- valign="top"
| 2
| NGI manager
| Within 10 working days NGI manager can suspend the site or ask to not suspend the site by providing adequate explanation<br>
|- valign="top"
| 3
| COD
|
*In the case of '''no''' NGI intervention, the site is suspended in GOC DB.
*In the case of NGI intervention:
**non suspension will occur if the COD team agree on the reasoning provided by the NGI (the Chief Operations Officer may be involved)
**if availability shows no improvement COD can suspend the site
|}
'''Recomputation precedure'''
In case of doubts about the validity of Availability/Reliability reports, a RC/NGI can request recomputations according to the procedure defined at [[PROC10]]
= Process of handling Core services Availability and Reliability  =
*'''Generation of statistics'''
Availability and reliability statistics are automatically generated the first week of the month by the [[External tools#Availability_Computation_Engine|Availability Computation Engine]] using the profile in pdf format and placed under [http://gvdev.cern.ch/GRIDVIEW/downloads/Reports/].
*'''Preliminary processing'''
Once the reports are generated, sanity checks are performed by EGI SA1 (Task TSA1.8). After this step is completed, statistics are uploaded into the EGI document server. Links to monthly statistics are provided on a regular basis at [[Availability and reliability monthly statistics|Availability and reliability monthly statistics page]].<br>
*'''Publication'''
An announcement of the new results is distributed by EGI SA1 (TSA1.8) to the NGI Operations Managers mailing list. COD (TSA1.7) is responsible of supervising statistics by chasing NGIs to provide comments in case thresholds are not met. This phase starts by filing a ticket to the COD Support Unit. The overall comments gathering process is handled through tickets.
== Entities involved in the procedure  ==
'''Central Operator on Duty (COD)''': team provided by EGI and responsible for handling Core services availability and reliability reports.
'''Core service administrator:'''&nbsp;person responsible for runnig Core service.
== Steps  ==
'''Handling of Core Services below targets'''<br>
{| class="wikitable"
|-
! Step#
! Responsible
! Action
|- valign="top"
| 1
| COD
|
Creates a GGUS ticket and assigned to the respective NGI, asking for explanation to be given.
The explanation must be produced within 10 working days since the ticket is received.
|- valign="top"
| 2
|
Core service <br>administrator
| Provides explanation and improvement plan to the GGUS ticket.<br>
|- valign="top"
| 3
| COD
|
*If the explanation is found satisfactory the ticket is closed.
*If the explanation is not given in due time, or the explanation is found inadequate, COD team will report it to the Chief Operations Officer.&nbsp;
|- valign="top"
| 4<br>
| COD<br>
| COD close the parent ticket when all child tickets have been closed and provide summary as a solution.
|}
<br>
'''Recomputation precedure'''
In case of doubts about the validity of Availability/Reliability reports, a RC/NGI can request recomputations according to the procedure defined at [[PROC10]]
= Known issues and recommendations to NGIs  =
#'''Newly certified sites''' will get inaccurate Availability/Reliability figures for the month they were certified and all months before that. ACE takes into account the Certification status of the site in GOCDB in order to decide if metrics should be calculated for the site. Because the Certification status history is not currently available in the operations tools, until a solution is implemented NGIs should check if they have sites affected by this issue and report it as explanation. ''More information at [https://gus.fzk.de/ws/ticket_info.php?ticket=60594] and [https://gus.fzk.de/ws/ticket_info.php?ticket=60925]. ''
#'''Recalculation''' - The calculations performed by ACE always take into account the information system status and GOCDB information at the time the calculation is performed, and not that of a certain checkpoint in the past. The implication of this is that any complete recalculation has the risk of altering the results for sites that had correct numbers in the first place. Thus until a solution is found, complete recalculations are avoided whenever possible, and errors are fixed on per site basis for those that have lower number than they should.
#'''Weighted availability''' is calculated by multiplying the number of logical CPUs a site published with the published HEPSPEC value in BDII. It is important that these numbers are correct, if HEPSPEC for a site is too high or too low (for example in case of mistake) the overall NGI wighted availability will be affected.
= Revision history  =
{| class="wikitable"
|-
! Version
! Authors
! Date
! Comments
|-
| <br>
| <br>
| <br>
| <br>
|}
<br>
<br>
[[Category:Operations_Procedures]]

Latest revision as of 09:42, 15 April 2022