Difference between revisions of "EGI-InSPIRE:SA1.7-QR16"
(Created page with "{{Template:Op menubar}} {{Template:Inspire_reports_menubar}} {{TOC_right}} = 1. Task Meetings = <!-- Notes. Report here all task-specific meetings held. This includes (a) face-t...") |
|||
Line 21: | Line 21: | ||
Note. This is a detailed account of progress over the previous quarter of activities within the task. | Note. This is a detailed account of progress over the previous quarter of activities within the task. | ||
PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (AVOID BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN AN OVERALL REPORT) | PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (AVOID BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN AN OVERALL REPORT) | ||
--> | --> | ||
'''Followup upgrades of unsupported software''' | |||
COD is involved in the process of retirement of obsolete middleware like SHA-2 noncompliant middleware. | |||
The majority of services were already upgraded. | |||
'''ROD performance index''' | |||
For background information on this, have a look at [[SA1.7-QR6]], section '''RP OLA and ROD metrics'''. | |||
Since October 2011 we have been asking all NGIs above 10 items in the COD dashboard duting one month about the explanation through GGUS, what was the reason of such result and how do you plan to improve the situation. Currently we are continuing to collect and investigate these metrics and also to correlate this with other metrics and see if we can draw some conclusions from them. | |||
'''Availability followup''' | |||
See [[SA1.7-QR6]] for more background information. COD has issued GGUS tickets to sites that are below 70% availability for more than three consecutive months that are eligible for suspension. | |||
'''Unknown Followup''' | |||
See [[SA1.7-QR6]] and [[SA1.7-QR6]] for more background information. In Q14 we have continued this activity. In addition, we have started discussions with the SAM nagios team to have a nagios probe that will raise alarms on the operations dashboard when the unknown percentage is higher than a certain threshold. This is still in progress. | |||
'''Followup NGI Core Services availability''' | |||
We have issued GGUS tickets to NGIs that do not meet the 99% availability requirement. In februari 2012 we have started up this activity. At first we have only submitted GGUS tickets to NGIs informing the of their low top-level BDII availability. This activity has been continued in this quarter. | |||
'''Nagios Probe working group''' | |||
No report received. | |||
= 3. Issues and Mitigation = <!-- fill the table below | = 3. Issues and Mitigation = <!-- fill the table below |
Revision as of 15:30, 7 May 2014
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Inspire reports menu: | Home • | SA1 weekly Reports • | SA1 Task QR Reports • | NGI QR Reports • | NGI QR User support Reports |
1. Task Meetings
Date (dd/mm/yyyy) | Url Indico Agenda | Title | Outcome |
---|---|---|---|
... | .... | ... | ... |
2. Main Achievements
Followup upgrades of unsupported software
COD is involved in the process of retirement of obsolete middleware like SHA-2 noncompliant middleware. The majority of services were already upgraded.
ROD performance index
For background information on this, have a look at SA1.7-QR6, section RP OLA and ROD metrics. Since October 2011 we have been asking all NGIs above 10 items in the COD dashboard duting one month about the explanation through GGUS, what was the reason of such result and how do you plan to improve the situation. Currently we are continuing to collect and investigate these metrics and also to correlate this with other metrics and see if we can draw some conclusions from them.
Availability followup
See SA1.7-QR6 for more background information. COD has issued GGUS tickets to sites that are below 70% availability for more than three consecutive months that are eligible for suspension.
Unknown Followup
See SA1.7-QR6 and SA1.7-QR6 for more background information. In Q14 we have continued this activity. In addition, we have started discussions with the SAM nagios team to have a nagios probe that will raise alarms on the operations dashboard when the unknown percentage is higher than a certain threshold. This is still in progress.
Followup NGI Core Services availability
We have issued GGUS tickets to NGIs that do not meet the 99% availability requirement. In februari 2012 we have started up this activity. At first we have only submitted GGUS tickets to NGIs informing the of their low top-level BDII availability. This activity has been continued in this quarter.
Nagios Probe working group
No report received.
3. Issues and Mitigation
Issue Description | Mitigation Description |
---|---|