Resource Centres OLA and Resource infrastructure Provider OLA reports
Tools and documentation
- xls availability/reliability report generator (based on Nagios results as of 1 June 2010)
- Availability/reliability computation algorithm
- OLD: EGEE-III Comments on site availability and reliability statistics
Note: in EGI sites do not need to provide comments anymore. In EGI comments will be solicited and collected through GGUS tickets instead.
Statistics
- May 2010 [1]
- January 2008 - April 2010 (EGEE league tables)
Description of the process
Generation of the results
Availability and reliability statistics are automatically generated the first few days of the month by GridView in pdf format and placed under [2]. An Excel version is available at [3]
Initial processing
Once the reports are generated, they are checked by EGI SA1 for any unusual values. After the check is complete, they are uploaded to the EGI document server, and they are linked from this wiki page.
Publication
An announcement of the new results is send then by EGI SA1 to the NOC managers mailing list. Also a ticket is opened to the COD in order to check for sites missing the Availability/Reliability targets, or meet the criteria for suspension.
Handling of results 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 assigned to appropriate NGI, asking for explanation to be given. The explanation must be procuded within 7 working days since the ticket has been opened. If the explanation is found satisfactory the ticket will be closed any further action. If explanation is not given within the deadline or the explanation is found inadequate, the EGI Chief Operations Officer can decide within 3 working days after the deadline if he/she objects to the site being added to the EGI "Hall of Shame" wiki page. After the 3 days pass, the site is added to the wiki "Hall of Shame" webpage, unless the EGI Chief Operations Officer objects or decides to accelerate the process. The child ticket can then be closed. The parent ticket will be closed when all child tickets have been closed.
Handling of results that meet suspension criteria
For a site that is eligible for suspension, a child ticket is opened by the COD team assigned to appropriate NGI, asking for explanation to be given. The explanation must be produced within 7 working days since the ticket has been opened. If the explanation is found satisfactory the ticket will be closed without any further action. If explanation is not given within the deadline or the explanation is found inadequate, the EGI Chief Operations Officer can decide within 3 working days after the deadline if he/she objects to the site being suspended. After the 3 days pass, the site is suspended, unless the EGI Chief Operations Officer objects or decides to accelerate the process. The child ticket can then be closed. The parent ticket will be closed when all child tickets have been closed.