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"
| Line 18: | Line 18: | ||
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. | 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 | 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 sites that need to provide comments in case thresholds are not met, and candidates sites 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 results below targets = | = Handling of results below targets = | ||
Revision as of 17:45, 25 June 2010
Tools and documentation
- xls availability/reliability report generator (providing access to the database including Nagios results for OPS and SAM results for VOs)
- 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 statistics
Availability and reliability statistics are automatically generated the first week of the month by GridView in pdf format and placed under [2]. An Excel version is available at [3]
- 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 sites that need to provide comments in case thresholds are not met, and candidates sites 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 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.