Difference between revisions of "WI03 RC and RP OLA violation report followup"
Line 124: | Line 124: | ||
|} | |} | ||
<br> <span style="color: rgb(255, 0, 0);">'''VERY IMPORTANT'''</span> | <br> <span style="color: rgb(255, 0, 0);">'''VERY IMPORTANT'''</span> | ||
Line 178: | Line 173: | ||
|} | |} | ||
= | = Ticket content = | ||
<pre>Subject:$SU/$siteName site suspension | <pre>Subject:$SU/$siteName site suspension | ||
Line 218: | Line 189: | ||
EGI Central Operator on Duty | EGI Central Operator on Duty | ||
</pre> | </pre> | ||
[[Ticket generator]] |
Revision as of 12:37, 27 November 2012
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
EGI Infrastructure Operations Oversight menu: | Home • | EGI.eu Operations Team • | Regional Operators (ROD) |
Internal procedure for COD - Availability and reliability work instruction 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 Underperforming_sites_and_suspensions page | ||
2 | Ava/Rel report review | ||
1 | Prepare 'sites for suspension' list: Look at availability metics for two previous months in AR report and the current one. If all are below 70% then sites qualifies for suspension.
Check if the site was mentioned in List of sites for which the availability followup procedures were not applicable page. In some cases there could be no need to open a ticket. | ||
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.
Check if the site was mentioned in List of sites for which the availability followup procedures were not applicable page In some cases there could be no need to open a ticket. | ||
3 | Create tickets for each case as a child to the tickets assigned to COD | ||
1 | For 'sites for suspension' list please use ticket generator | ||
2 | For 'sites to be asked for explanation' list please use ticket generator | ||
Within 10 working days from when the tickets are created. | 4 |
Handling of sites below targets When explanation is provided and is found satisfactory put as a solution of the ticket 'The explanation is satisfactory. Thank you!'. After that you should set child ticket to 'verified' status. | |
After 10 working days from when the tickets are created. | 5 | Final actions. | |
1 | Handling of sites that are eligible for suspension
| ||
2 | Handling of sites below targets
If the explanation is not given in due time, or the explanation is found inadequate, COD send mail to NGI/ROC manager with CC to ROD and GGUS:
Dear XX I would like to inform you that 10 working days passed. Please make the site react on the ticket or suspend the site within 3 days. If NGI will not react COD will suspend the site on the 4th day. Best Regards XXX On behalf of COD team | ||
6 | Prepare summary report (it should be placed in parent ticket):
| ||
7 | Update List of sites for which the availability followup procedures were not applicable page. Put here outstanding cases which should be recorded. This could be used for example to avoid opening a ticket next month for a solved issue. | ||
8 | Update Underperforming_sites_and_suspensions page. |
VERY IMPORTANT
In grid view NGIs/ROCs are named differently then in GGUS. You should change NGI/ROC name according to GGUS.
GGUS | Gridview |
---|---|
ROC_DECH | GermanySwitzerland |
NGI_FRANCE | NGI_France |
NGI_CYGRID | NGI_CY |
ROC_Asia/Pacific | AsiaPacific |
ROC_Italy | Italy |
ROC_CERN | CERN |
ROC_Russia | Russia |
ROC_North | NorthernEurope |
ROC_UK/Ireland | UKI |
ROC_SE | SouthEasternEurope |
ROC_SW | SouthWesternEurope |
NGI_UA | Ukraine |
Ticket content
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: [[Availability_and_reliability_monthly_statistics]]. According to procedures approved on OMB 17.08, site will be suspended within 10 working days unless the NGI intervene. If you think that the site should not be suspended please provide justification within 10 working days. Best Regards, EGI Central Operator on Duty