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 61: | Line 61: | ||
| | | | ||
|1 | |1 | ||
| Close all open tickets. | |||
|- | |||
| | |||
| | |||
|2 | |||
| Suspend in GOC DB sites from '''sites for suspension'''' list qualified for suspension. | | Suspend in GOC DB sites from '''sites for suspension'''' list qualified for suspension. | ||
|- | |- | ||
| | | | ||
| | | | ||
| | |3 | ||
| | | 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 | ||
| Line 72: | Line 77: | ||
|- | |- | ||
|} | |} | ||
= Tickets content = | = Tickets content = | ||
Revision as of 14:18, 23 July 2010
Internal procedure for COD
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:
| Timelines | Step | Substep | Description |
|---|---|---|---|
| 1 | Add ticket url to Availability and reliability internal procedure for COD tickets page | ||
| 2 | Ava/Rel report review | ||
| 1 | Prepare 'sites for suspension' list: Look at two previous months in AR report and the current one. If all are below 50% then sites qualifies for suspension. | ||
| 2 | Prepare 'sites to be asked for explanation' list: Look at current months in AR report. If Ava. is below 70% or Rel. below 75% then sites qualifies to be asked for explanation. This list should be prepared according to requirements for input file for ticket generator | ||
| 3 | Create tickets for each case as a child to the tickets assigned to COD | ||
| 1 | For 'sites for suspension' list please use template Site for suspension | ||
| 2 | For 'sites to be asked for explanation' list please use ticket generator | ||
| Within 7 working days from when the tickets are created. | 4 | When explanation is provided and is found satisfactory, you should set child ticket to 'verified' status. | |
| After 7 working days from when the tickets are created. | 5 | Final action. | |
| 1 | Close all open tickets. | ||
| 2 | Suspend in GOC DB sites from sites for suspension' list qualified for suspension. | ||
| 3 | Prepare summary report of explanations (it should be placed in parent ticket):
|
Tickets content
Request for explanation
Subject:$SU/$siteName - availability/reliability statistics for $date Dear $SU, According to recent availability/reliability report $siteName has achieved poor performance Ava. $availability Rel. $realiability. More details: https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_statistics. Could you please provide explanations for poor performance of the $siteName site? Your explanation must be returned within 7 working days from when the ticket is created. If the explanation is not given in due time, or the explanation is found inadequate, the EGI Chief Operations Officer can decide within 3 working days after the deadline to suspend the site. Best Regards, EGI Central Operator on Duty
Site for suspension
Subject:$SU/$siteName site suspension Dear $SU, According to recent availability/reliability report $siteName has achieved poor performance below target Ava. 50% or Rel. 50% in three consecutive months. More details: https://wiki.egi.eu/wiki/Availability_and_reliability_monthly_statistics. According to procedures site will be suspended within 7 working days unless the NGI intervene. If you think that the site should not be suspended please provide justification within 7 working days. Best Regards, EGI Central Operator on Duty
How to use ticket generator
to be done