Resource Centres OLA and Resource infrastructure Provider OLA reports

Main

EGI.eu operations services

Support

Documentation

Tools

Activities

Performance

Technology

Catch-all Services

Resource Allocation

Security

EGI Performance is measured using two parameters: Availability and Reliability (definition).

Availability/Reliability data is provided by the 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 metric results are used for the calculation of Availability/Reliability.

Go to the main page for information on service level targets and related statistics.

Performance reports

Resource Centres

January 2008 - April 2010 (EGEE)

Availability/Reliability	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2010	-	-	-	-	05/10	06/10	07/10	08/10	09/10	10/10	11/10	12/10
2011	01/11	02/11	03/11	04/11	05/11	06/11	07/11	08/11	09/11	10/11	11/11	12/11
2012	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 Infrastructures

Service Level: top-BDII Availability/Reliability

Jan

Feb

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

Nov

Dec

2011

-

-

-

-

-

-

-

-

09/11

10/11

11/11

12/11

2012

01/12

02/12

03/12

04/12

05/12

06/12

07/12

[08/12]

[09/12]

[10/12]

[11/12]

[12/12]

Service Level: ROD Performance Index ticket/Report

Jan

Feb

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

Nov

Dec

2011

-

-

-

-

-

-

-

-

-

76116 10/11

77235 11/11

78078 12/11

2012

78078 01/12

79006 02/12

80841/ 03/12

81998/ 04/12

82926/ 05/12

84168/ 06/12

85127/ 07/12

[GGUS]/ [08/12]

[GGUS]/ [09/12]

[GGUS]/ [10/12]

[GGUS]/ [11/12]

[GGUS]/ [12/12]

EGI overall Availability and Reliability

It is available here (xls file, data from May 01 2010)

Underperforming/Suspended RCs

• List of underperforming/suspended Resource Centres
• List of Rsource Centres to which the Availability followup procedure was not applicable

Process for quality verification

• Generation of statistics

Availability and reliability statistics are automatically generated the first week of the month by the Availability Computation Engine (Gridview until May 2011) using the profile in pdf format and placed under [1].

• 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:

1. a child ticket is opened by the COD team and assigned to the respective NGI, asking for explanation to be given
2. the explanation must be produced within 10 working days since the ticket is received by the site (please see known issues section [2]). Reminders and escalation is performed in accordance to COD escalation procedures [3].
3. if the explanation is found satisfactory the ticket is closed
4. conversely if the explanation is not given in due time, or the explanation is found inadequate, COD escalation procedure will be followed [4], with the site being suspended if neither site or NGI reply to the ticket
5. the child ticket can then be closed
6. 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:

1. 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 [5])
2. after the 10 days period passes during which normal COD escalation procedures apply [6], the site is suspended by COD unless the NGI has intervened or the EGI Chief Operations officer objects.
3. in the case of NGI intervention, non suspension will occur if both the COD and COO agree on the reasoning provided by the NGI
4. the child ticket closes either when the site is suspended or when suspension is canceled
5. 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 [7]

• 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 [8]

Known issues and recommendations to NGIs

1. 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 [9] and [10]. 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.
2. 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.
3. 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.

Links

• Definition of Availability and Reliability and related computation algorithm (paper)

• NEW! List of Nagios tests used for availability computation
• Availability Computation Engine (ACE) home page

• COD procedure for oversight of availability and reliability performance
• Impact of change of suspension policy for under-performing sites: report