Difference between revisions of "WI03 RC and RP OLA violation report followup"
Jump to navigation
Jump to search
NGI managers email (example)
Line 121: | Line 121: | ||
According to recent availability/reliability report following sites have achieved insufficient performance below Availability target threshold in 3 consecutive months (November, December, January): | According to recent availability/reliability report following sites have achieved insufficient performance below Availability target threshold in 3 consecutive months (November, December, January): | ||
* site name | * site name | ||
* | * | ||
* | * |
Revision as of 13:32, 16 March 2015
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) |
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)
Subject: $NGI_SU - $date - RP/RC OLA performance Dear NGI, According to the Service targets reports for Resource infrastructure Provider [1] and Resource Center[2] OLA for '''January '''following problems occurred: Report: https://documents.egi.eu/document/2423 ============= RC Availability Reliability [2]========== According to recent availability/reliability report following sites have achieved insufficient performance below Availability target threshold in 3 consecutive months (November, December, January): * site name * * * The sites will be suspended 10 working days after receiving this ticket unless NGI intervene. * 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. ============= RP Availability Reliability [1]========== According to recent availability/reliability report the sites operated by your Operations Center have achieved insufficient average performance: - Availability: - Reliability: We would like to kindly ask you to take an action to improve your Resource Infrastructure performance. ============= RP Unknown [1]========== Unknown metric in your NGI has been spotted with higher than 10% value. Note: Having a high percentage of UNKNOWN status of sites implies that there is no data available regarding the site availability for a substantial amount of time. For more information about UNKNOWN status please visit [6] We would like to kindly ask you to take an action to decrease Unknown metric. ============= Top BDII Availability Reliability [1]========== According to availability/reliability Top Level BDII report your Top Level BDII achieved insufficient performance: - Availability: - Reliability: We would like to kindly ask you to take an action to improve your Top-BDII performance. Note: If the top-BDII performance was due to problems with middleware or you believe there are errors in the computation, please send a GGUS ticket to the Service Level Management support unit, following the procedure [4] If you need information on how to set up a highly available Top-BDII, have a look at [5] ============= SAM Availability Reliability [1]========== According to availability/reliability SAM report your NGI SAM instance achieved insufficient performance: - Availability: - Reliability: We would like to kindly ask you to take an action to improve your NGI SAM performance. ============= 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): ********************** 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 [2] https://documents.egi.eu/public/ShowDocument?docid=31 [3] https://wiki.egi.eu/wiki/PROC01 [4] https://wiki.egi.eu/wiki/PROC10 [5] https://wiki.egi.eu/wiki/MAN05 [6] https://wiki.egi.eu/wiki/Unknown_issue Best Regards, EGI Operations
More info about Ticket generator for A/R