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 "WI03 RC and RP OLA violation report followup"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
# add ticket url to [https://wiki.egi.eu/wiki/Availability_and_reliability_internal_procedure_for_COD_tickets Availability and reliability internal procedure for COD tickets] page | # add ticket url to [https://wiki.egi.eu/wiki/Availability_and_reliability_internal_procedure_for_COD_tickets Availability and reliability internal procedure for COD tickets] page | ||
# review Ava/Rel report and prepare following lists: | # review Ava/Rel report and prepare following lists: | ||
* CASE 1: sites for suspension (Look at two previous months in AR report and the current one. If all are below 50% then sites qualifies for suspension.) | ** CASE 1: sites for suspension (Look at two previous months in AR report and the current one. If all are below 50% then sites qualifies for suspension.) | ||
* CASE 2: sites to be asked for explanation (below 75% for reliability and 70% for availability) | ** CASE 2: sites to be asked for explanation (below 75% for reliability and 70% for availability) | ||
# Generate child tickets for both lists | # Generate child tickets for both lists | ||
* for CASE1: when explanation was provided and is found satisfactory, set child ticket to 'verified' status | ** for CASE1: when explanation was provided and is found satisfactory, set child ticket to 'verified' status | ||
# When the deadline (7 working days) expired: | # When the deadline (7 working days) expired: | ||
* suspend in GOC DB sites qualified for suspension | ** suspend in GOC DB sites qualified for suspension | ||
* prepare summary report of explanations (it should be placed in parent ticket): | ** prepare summary report of explanations (it should be placed in parent ticket): | ||
** sites which are not responsive | *** sites which are not responsive | ||
** sites which provided not satisfactory explanation | *** sites which provided not satisfactory explanation | ||
** ROCs/NGIs which are not responsive | *** ROCs/NGIs which are not responsive | ||
Revision as of 11:50, 23 July 2010
Under Construction
This page describes steps which should be taken by COD shifter to follow availability/reliability issues.
When GGUS ticket about availability/reliability metrics is assigned to COD:
- add ticket url to Availability and reliability internal procedure for COD tickets page
- review Ava/Rel report and prepare following lists:
- CASE 1: sites for suspension (Look at two previous months in AR report and the current one. If all are below 50% then sites qualifies for suspension.)
- CASE 2: sites to be asked for explanation (below 75% for reliability and 70% for availability)
- Generate child tickets for both lists
- for CASE1: when explanation was provided and is found satisfactory, set child ticket to 'verified' status
- When the deadline (7 working days) expired:
- suspend in GOC DB sites qualified for suspension
- prepare summary report of explanations (it should be placed in parent ticket):
- sites which are not responsive
- sites which provided not satisfactory explanation
- ROCs/NGIs which are not responsive