Difference between revisions of "WI03 RC and RP OLA violation report followup"
Jump to navigation
Jump to search
NGI managers email (example)
(9 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:Op menubar}} {{Template:GO menubar}} {{TOC_right}} | {{Template:Op menubar}} {{Template:GO menubar}} {{TOC_right}} | ||
[[Category:Deprecated]] | |||
{| style="border:1px solid black; background-color:lightgrey; color: black; padding:5px; font-size:140%; width: 90%; margin: auto;" | |||
| style="padding-right: 15px; padding-left: 15px;" | | |||
|[[File:Alert.png]] This article is '''Deprecated''' and should no longer be used, but is still available for reasons of reference. | |||
|} | |||
<br> | <br> | ||
Line 110: | Line 114: | ||
</pre> | </pre> | ||
=== GGUS Ticket content (template) === | === GGUS Ticket content (template) === | ||
<pre> | <pre>$NGI - $MONTH $YEAR - RP/RC OLA performance | ||
Dear NGI, | Dear NGI/ROC, | ||
the EGI RC OLA and RP OLA Report for November 2020 has been produced and is available at the following links: | |||
- NGIs reports: http://egi.ui.argo.grnet.gr/egi/report-ar/Critical/NGI?month=2020-11 (Clicking on the NGI name, it will be displayed the resource centres A/R figures) | |||
- RCs reports: http://egi.ui.argo.grnet.gr/egi/report-ar/Critical/SITES?month=2020-11 | |||
According to the Service targets reports for Resource infrastructure Provider [1] and Resource Centre[2] OLAs, the following problems occurred: | |||
============= RC Availability Reliability [2]========== | ============= RC Availability Reliability [2]========== | ||
According to recent availability/reliability report following sites have achieved insufficient performance below Availability target threshold in 3 consecutive months ( | According to recent availability/reliability report following sites have achieved insufficient performance below Availability target threshold in 3 consecutive months (September, October, and November): | ||
$SITE | |||
$SITE | |||
$SITE | |||
* | * During the 10 working days after receiving this ticket the NGI can suspend the site or ask to not suspend the site by providing adequate explanation. If no answer is provided to this ticket, the NGI will be contacted by email; if no reply will be provided to the email, the site will be suspended[6]. | ||
If NGI intervene and performance is still below targets 3 days after the intervention, the site will also be suspended. | If NGI intervene and performance is still below targets 3 days after the intervention, the site will also be suspended. | ||
If you think that the site should not be suspended please provide justification in this ticket within 10 working days. In case the site performance rises above targets within 3 days from providing explanation, the site will not be suspended. Otherwise EGI Operations may decide on suspension of the site. | If you think that the site should not be suspended please provide justification in this ticket within 10 working days. In case the site performance rises above targets within 3 days from providing explanation, the site will not be suspended. Otherwise EGI Operations may decide on suspension of the site. | ||
Line 183: | Line 148: | ||
top priority (expected 1 working day): | top priority (expected 1 working day): | ||
In order to see the details (https://wiki.egi.eu/wiki/Service_Level_Target_-_Quality_of_Support ): | |||
1) go on https://ggus.eu/?mode=report_view | |||
2) choose "response times" or "tickets submitted" and the proper timeframe | |||
3) select your NGI | |||
4) group by Responsible unit and priority | |||
5) click on the lines displayed for getting the tickets details | |||
Please investigate the reasons for mentioned above situation and provide an explanation for each case in this ticket within 10 days from receiving it. | Please investigate the reasons for mentioned above situation and provide an explanation for each case in this ticket within 10 days from receiving it. | ||
Line 195: | Line 166: | ||
Links: | Links: | ||
[1] https://documents.egi.eu/public/ShowDocument?docid=463 | [1] https://documents.egi.eu/public/ShowDocument?docid=463 "Resource infrastructure Provider Operational Level Agreement" | ||
[2] https://documents.egi.eu/public/ShowDocument?docid=31 | [2] https://documents.egi.eu/public/ShowDocument?docid=31 "Resource Centre Operational Level Agreement" | ||
[3] https://wiki.egi.eu/wiki/PROC01 | [3] https://wiki.egi.eu/wiki/PROC01 "EGI Infrastructure Oversight escalation" | ||
[4] https://wiki.egi.eu/wiki/PROC10 | [4] https://wiki.egi.eu/wiki/PROC10 "Recomputation of SAM results or availability reliability statistics" | ||
[5] https://wiki.egi.eu/wiki/MAN05 | [5] https://wiki.egi.eu/wiki/MAN05 "top-BDII and site-BDII High Availability" | ||
[6] https://wiki.egi.eu/wiki/ | [6] https://wiki.egi.eu/wiki/PROC04 "Quality verification of monthly availability and reliability statistics" | ||
Best Regards, | Best Regards, |
Latest revision as of 16:18, 30 July 2021
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) |
This article is Deprecated and should no longer be used, but is still available for reasons of reference. |
RC and RP OLA violation work instruction for EGI Operations
This page describes steps which should be taken to follow RC and RP OLA violation issues.
General info
- Receiver: NGI
- Subject: RC and RP OLA violation
- Threshold:
- Goal: We expect to see improvement
- Deadline for answers: 10 days
- No response:
Steps
Starts with 1 day of the month
Step [#] |
Max. Duration [work days] (time before moving to next step) |
Responsible | Step | |
1 |
1 | 10 |
SLM, CA |
|
2 |
PS |
| ||
3 | MK |
| ||
2 |
10 |
VS |
|
NGI managers email (example)
Subject: EGI RC OLA and RP OLA Reports for October 2014 Content: Dear NGI managers Please find EGI RC OLA and RP OLA Reports for October 2014 under: https://documents.egi.eu/public/ShowDocument?docid=2352 Entry includes reports: * EGI Cloud RC A/R * EGI RP/RC A/R/U * EGI RP Quality of Support * EGI RP ROD performance index * EGI RP SAM A/R * EGI RP Top-BDII A/R Best Regards
DOC DB content (example)
Title: EGI RC OLA and RP OLA Reports for October 2014 Abstract: Container for reports supporting Resource Centre Operational Level Agreement https://documents.egi.eu/document/31 and Resource infrastructure Provider Operational Level Agreement https://documents.egi.eu/document/463
GGUS Ticket content (template)
$NGI - $MONTH $YEAR - RP/RC OLA performance Dear NGI/ROC, the EGI RC OLA and RP OLA Report for November 2020 has been produced and is available at the following links: - NGIs reports: http://egi.ui.argo.grnet.gr/egi/report-ar/Critical/NGI?month=2020-11 (Clicking on the NGI name, it will be displayed the resource centres A/R figures) - RCs reports: http://egi.ui.argo.grnet.gr/egi/report-ar/Critical/SITES?month=2020-11 According to the Service targets reports for Resource infrastructure Provider [1] and Resource Centre[2] OLAs, the following problems occurred: ============= RC Availability Reliability [2]========== According to recent availability/reliability report following sites have achieved insufficient performance below Availability target threshold in 3 consecutive months (September, October, and November): $SITE $SITE $SITE * During the 10 working days after receiving this ticket the NGI can suspend the site or ask to not suspend the site by providing adequate explanation. If no answer is provided to this ticket, the NGI will be contacted by email; if no reply will be provided to the email, the site will be suspended[6]. If NGI intervene and performance is still below targets 3 days after the intervention, the site will also be suspended. If you think that the site should not be suspended please provide justification in this ticket within 10 working days. In case the site performance rises above targets within 3 days from providing explanation, the site will not be suspended. Otherwise EGI Operations may decide on suspension of the site. ============= Quality of Support [1]========== According to recent report your NGI achieved insufficient Quality of Support performance: less urgent (expected 5 working days): urgent (expected 5 working days): very urgent (expected 1 working day): top priority (expected 1 working day): In order to see the details (https://wiki.egi.eu/wiki/Service_Level_Target_-_Quality_of_Support ): 1) go on https://ggus.eu/?mode=report_view 2) choose "response times" or "tickets submitted" and the proper timeframe 3) select your NGI 4) group by Responsible unit and priority 5) click on the lines displayed for getting the tickets details Please investigate the reasons for mentioned above situation and provide an explanation for each case in this ticket within 10 days from receiving it. If no explanation is provided, the EGI Operation will be informed about the situation and may take further steps. ********************** Links: [1] https://documents.egi.eu/public/ShowDocument?docid=463 "Resource infrastructure Provider Operational Level Agreement" [2] https://documents.egi.eu/public/ShowDocument?docid=31 "Resource Centre Operational Level Agreement" [3] https://wiki.egi.eu/wiki/PROC01 "EGI Infrastructure Oversight escalation" [4] https://wiki.egi.eu/wiki/PROC10 "Recomputation of SAM results or availability reliability statistics" [5] https://wiki.egi.eu/wiki/MAN05 "top-BDII and site-BDII High Availability" [6] https://wiki.egi.eu/wiki/PROC04 "Quality verification of monthly availability and reliability statistics" Best Regards, EGI Operations
More info about Ticket generator for A/R