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 "Resource Centres OLA and Resource infrastructure Provider OLA reports"

From EGIWiki
Jump to navigation Jump to search
(Replaced content with "see https://confluence.egi.eu/display/EGISLM/RC+OLA+and+RIP+OLA+reports")
Tag: Replaced
 
(276 intermediate revisions by 18 users not shown)
Line 1: Line 1:
{{Template:Op menubar}}
see https://confluence.egi.eu/display/EGISLM/RC+OLA+and+RIP+OLA+reports
[[Category:Procedures]]
[[Category:Service Level Management]]
{{TOC_right}}
 
Go to the '''[[Performance|main]]''' page for information on service level targets and related statistics.
 
= Introduction =
EGI Performance is measured using two parameters: Availability and Reliability ([https://tomtools.cern.ch/confluence/download/attachments/2261694/Ace_Service_Availability_Computation.pdf?version=1&modificationDate=1314361543000 definition]).
 
Availability/Reliability data is provided by the [https://grid-monitoring.egi.eu/myegi/sa/ MyEGI] portal. Note: GridView Availability/Reliability views are now obsolete.
 
Availability/Reliability are measured at a Resource Centre (RC) level and at a Resource infrastructure Provider (RP) level (for NGIs and EIROs).
 
[[SAM_Tests|SAM metric]] results are used for the calculation of Availability/Reliability.
 
= Performance reports=
 
== 2012 ==
 
=== Resource Centre Performance ===
{| border="1" cellspacing="0" cellpadding="5"
|-<!--style="background-color: lightgray;"-->
| '''Service Level'''
|'''Jan'''
|'''Feb'''
|'''Mar'''
|'''Apr'''
|'''May'''
|'''Jun'''
|'''Jul'''
|'''Aug'''
|'''Sep'''
|'''Oct'''
|'''Nov'''
|'''Dec'''
|-
| '''Availability/Reliability'''
|[https://documents.egi.eu/document/1000 01/12]
|[ 02/12]
|[ 03/12]
|[ 04/12]
|[ 05/12]
|[ 06/12]
|[ 07/12]
|[ 08/12]
|[ 09/12]
|[ 10/12]
|[ 11/12]
|[ 12/12]
|}
 
=== Resource infrastructure Provider Performance  ===
 
{| cellspacing="0" cellpadding="5" border="1"
|-
| '''Service Level'''
| '''Jan'''
| '''Feb'''
| '''Mar'''
| '''Apr'''
| '''May'''
| '''Jun'''
| '''Jul'''
| '''Aug'''
| '''Sep'''
| '''Oct'''
| '''Nov'''
| '''Dec'''
|-
| '''top-BDII Availability/Reliability'''
| [https://documents.egi.eu/secure/RetrieveFile?docid=1000&version=1&filename=EGI-core_services_availabilities-per_NGI-Jan2012.pdf 01/12]
| [02/12]
| [03/12]
| [04/12]
| [05/12]
| [06/12]
| [07/12]
| [08/12]
| [09/12]
| [10/12]
| [11/12]
| [12/12]
|-
| '''ROD Performance Index'''
| [https://ggus.eu/ws/ticket_info.php?ticket=79006 GGUS-79006]
[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2001-2012.pdf Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
| [GGUS0 n]
[Newsletter]
 
|}
 
== 2011 ==
 
=== Resource Centre Performance ===
{| border="1" cellspacing="0" cellpadding="5"
|-<!--style="background-color: lightgray;"-->
| '''Service Level'''
|'''Jan'''
|'''Feb'''
|'''Mar'''
|'''Apr'''
|'''May'''
|'''Jun'''
|'''Jul'''
|'''Aug'''
|'''Sep'''
|'''Oct'''
|'''Nov'''
|'''Dec'''
|-
| '''Availability/Reliability'''
|[https://documents.egi.eu/document/332 01/11]
|[https://documents.egi.eu/document/402 02/11]
|[https://documents.egi.eu/document/465 03/11]
|[https://documents.egi.eu/document/508 04/11]
|[https://documents.egi.eu/document/593 05/11]
|[https://documents.egi.eu/document/648 06/11]
|[https://documents.egi.eu/document/716 07/11]
|[https://documents.egi.eu/document/783 08/11]
|[https://documents.egi.eu/document/820 09/11]
|[https://documents.egi.eu/document/879 10/11]
|[https://documents.egi.eu/document/905 11/11]
|[https://documents.egi.eu/document/959 12/11]
|}
 
=== Resource infrastructure Provider Performance  ===
 
{| cellspacing="0" cellpadding="5" border="1"
|-
| '''Service Level'''
| '''Sep'''
| '''Oct'''
| '''Nov'''
| '''Dec'''
|-
| '''top-BDII Availability/Reliability'''
| <!--Sep--> [https://documents.egi.eu/public/RetrieveFile?docid=820&version=5&filename=EGI-core_services_availabilities-per_NGI%20NGIs%20core%20services.pdf Sep]
| <!--Oct--> [https://documents.egi.eu/public/RetrieveFile?docid=879&version=4&filename=EGI-core_services_availabilities-per_NGI-Oct2011-1.pdf Oct]
| <!--Nov--> [https://documents.egi.eu/public/RetrieveFile?docid=905&version=3&filename=EGI-core_services_availabilities-per_NGI-Nov2011.pdf Nov]
| <!--Dec--> [https://documents.egi.eu/public/RetrieveFile?docid=959&version=1&filename=EGI-core_services_availabilities-per_NGI-Dec2011.pdf Dec]
|-
| '''ROD Performance Index'''
| <!--Sep-->NA
| <!--Oct-->[https://ggus.eu/ws/ticket_info.php?ticket=76116 GGUS-76116]
[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2011-2011.pdf Newsletter]
 
| <!--Nov-->[https://ggus.eu/ws/ticket_info.php?ticket=77235 GGUS-77235]
[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2012-2011.pdf Newsletter]
 
| <!--Dec--> [https://ggus.eu/ws/ticket_info.php?ticket=78078 GGUS-78078]
[https://documents.egi.eu/secure/RetrieveFile?docid=298&version=1&filename=ROD%20newsletter%2012-2011.pdf Newsletter]
 
|}
 
== 2010 ==
<!--*[https://documents.egi.eu/document/42 May]|[https://documents.egi.eu/document/96 Jun]|[https://documents.egi.eu/document/130 Jul]|[https://documents.egi.eu/document/157 Aug]|[https://documents.egi.eu/document/219 Sep]|[https://documents.egi.eu/document/238 Oct]|[https://documents.egi.eu/document/266 Nov]|[https://documents.egi.eu/document/299 Dec]
*[https://edms.cern.ch/document/963325 January 2008 - April 2010] (EGEE league tables)-->
 
 
=== Resource Centre Performance ===
{| border="1" cellspacing="0" cellpadding="5"
|-<!--style="background-color: lightgray;"-->
| '''Service Level'''
|'''EGEE Statistics'''
|'''May'''
|'''Jun'''
|'''Jul'''
|'''Aug'''
|'''Sep'''
|'''Oct'''
|'''Nov'''
|'''Dec'''
|-
| '''Availability/Reliability'''
|[https://edms.cern.ch/document/963325 January 2008 - April 2010]
|[https://documents.egi.eu/document/42 05/10]
|[https://documents.egi.eu/document/96 06/10]
|[https://documents.egi.eu/document/130 07/10]
|[https://documents.egi.eu/document/157 08/10]
|[https://documents.egi.eu/document/219  09/10]
|[https://documents.egi.eu/document/238 10/10]
|[https://documents.egi.eu/document/266 11/10]
|[https://documents.egi.eu/document/299 12/10]
|}
 
 
 
== EGI overall Availability and Reliability ==
It is available [https://documents.egi.eu/public/ShowDocument?docid=415 here] (xls file, data from May 01 2010)
 
== Underperforming/Suspended RCs ==
* List of [https://wiki.egi.eu/wiki/Availability_and_reliability_reports_metrics underperforming/suspended Resource Centres ]
* List of [https://wiki.egi.eu/wiki/List_of_sites_for_which_the_availability_followup_procedures_were_not_applicable Rsource Centres] to which the Availability followup procedure was not applicable
<!--* [https://twiki.cern.ch/twiki/bin/view/EGEE/SuspendedSites List of suspended sites (2009)]-->
 
=Process for quality verification=
 
* '''Generation of statistics'''
Availability and reliability statistics are automatically generated the first week of the month by the [https://wiki.egi.eu/wiki/External_tools#Availability_Computation_Engine Availability Computation Engine] (Gridview until May 2011) using the profile  in pdf format and placed under [http://gvdev.cern.ch/GRIDVIEW/downloads/Reports/]. An Excel version is available at [http://gvdev.cern.ch/GVPC/Excel/ACE/]
 
* '''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 will be provided on a regular basis at this wiki page.
 
* '''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 chase sites that need to provide comments in case thresholds are not met, and identifies sites eligible for suspension. This phase starts by filing a ticket to the COD Support Unit. The overall comments gathering process is handled through tickets.
 
* '''Handling of sites below targets'''
For a site that misses availability/reliability targets but is not eligible for suspension:
 
# a child ticket is opened by the COD team 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 by the site (please see known issues section [https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_statistics#Known_issues_and_recommendations_to_NGIs]). Reminders and escalation is performed in accordance to COD escalation procedures [https://wiki.egi.eu/wiki/Operations:COD_Escalation_Procedure].
# if the explanation is found satisfactory the ticket is closed
# conversely if the explanation is not given in due time, or the explanation is found inadequate, COD escalation procedure will be followed [https://wiki.egi.eu/wiki/Operations:COD_Escalation_Procedure], with the site being suspended if neither site or NGI reply to the ticket
# the child ticket can then be closed
# the parent ticket will be closed when all child tickets have been closed.
 
* '''Handling of sites that are eligible for suspension'''
For a site that is eligible for suspension:
# a child ticket is opened by the COD team assigned to appropriate NGI, notifying that the site will be suspended within 10 working days (please see known issues section [https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_statistics#Known_issues_and_recommendations_to_NGIs])
# after the 10 days period passes during which normal COD escalation procedures apply [https://wiki.egi.eu/wiki/Operations:COD_Escalation_Procedure], the site is suspended by COD unless the NGI has intervened or the EGI Chief Operations officer objects.
# in the case of NGI intervention, non suspension will occur if both the COD and COO agree on the reasoning provided by the NGI
# the child ticket closes either when the site is suspended or when suspension is canceled
# the parent ticket will be closed when all child tickets have been closed
 
* '''Wiki follow up page'''
Sites that fail to provide explanations justifying the failure to meet OLA targets, or the explanation is found inadequate, as well as sites that are suspended, will be recorded in a wiki page [https://wiki.egi.eu/wiki/Availability_and_reliability_internal_procedure_for_COD_metrics]
 
* '''Recomputation precedure'''
Should there be doubts about the validity of Availability/Reliability reports, a RC/NGI can request recomputations according to the procedure defined at [https://wiki.egi.eu/wiki/PROC10]
 
=Known issues and recommendations to NGIs=
# ACE as Gridview in the past, is always calculating reliability and reliability of a site as soon as it shows up in GOCDB and in the BDIIs, regardless of its certification status. While processing the data in order to generate the availability/reliability report, ACE takes into account the Certification status of the site at that moment in order to decide if the site is certified and as a result it will show up in the report, or if it uncertified and it has to be excluded. '''Thus newly certified sites will get inaccurate Availability/Reliability figures for the month they were certified and all months before that.''' 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]. '''As of December 2010, Gridview had included a snapshot feature so availability takes into account the topology at the last day of the month. While it does not solve the problem completely, it reduces its impact. However ACE reports (used since May 2011) do not include the snapshot feature yet.'''
# 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. 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.
 
=[[Documentation#OLAs|Operational Level Agreements]]=
 
=Links=
* Definition of Availability and Reliability and related computation algorithm  ([https://tomtools.cern.ch/confluence/download/attachments/2261694/Ace_Service_Availability_Computation.pdf?version=1&modificationDate=1314361543000 paper])
 
* NEW! [https://wiki.egi.eu/wiki/Availability_and_reliability_tests List of Nagios tests] used for availability computation
* [https://tomtools.cern.ch/confluence/display/SAM/ACE Availability Computation Engine (ACE) home page]
 
*[https://wiki.egi.eu/wiki/Availability_and_reliability_internal_procedure_for_COD COD procedure for oversight of availability and reliability performance]
* Impact of change of suspension policy for under-performing sites: [https://wiki.egi.eu/wiki/Availability_and_reliability_threshold_change_impact report]
 
<!-- DEPRECATED LINKS
* [https://twiki.cern.ch/twiki/pub/LCG/GridView/Gridview_Service_Availability_Computation.pdf paper]
* [https://twiki.cern.ch/twiki/bin/view/LCG/ACE (Old) Availability Computation Engine] (ACE)
* [https://twiki.cern.ch/twiki/bin/view/EGEE/MonthlyAvailability EGEE-III Comments on site availability and reliability statistics]
*[http://gvdev.cern.ch/GVPC/Excel/ '''(DEPRECATED)''' GridView availability/reliability report generator] (providing access to the database including Nagios results for OPS and  SAM results for VOs)
*[http://gridview015.cern.ch/GVPC/Excel/ACE/ ACE report generator]
*[https://gvdev.cern.ch/ACEVAL/ace_index.php ACE visualization portal]-->
{{Template:Creative_commons}}

Latest revision as of 14:15, 25 August 2020