Difference between revisions of "EGI-InSPIRE:SA1.7-QR11"
Line 29: | Line 29: | ||
'''Followup upgrades of unsupported software''' | '''Followup upgrades of unsupported software''' | ||
There were quite a large number of sites that were still running glite-3.1 and glite-3.2 software that is no longer supported. | There were quite a large number of sites that were still running glite-3.1 and glite-3.2 software that is no longer supported. Last quarter a campaign was started to make these sites upgrade their services that run this software. This campaign was continued this quarter. COD has requested RODs to issued GGUS tickets to these sites and is following this up. | ||
'''ROD teams newsletter''' | '''ROD teams newsletter''' | ||
This quarter we have published a ROD teams newsletter in | This quarter we have published a ROD teams newsletter in Januaryr. The rationale behind the newsletter is descibed in the [[SA1.7-QR4]] report. | ||
'''ROD performance index''' | '''ROD performance index''' | ||
For background information on this, have a look at [[SA1.7-QR6]], section '''RP OLA and ROD metrics'''. | 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 | 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''' | '''Availability followup''' | ||
See [[SA1.7-QR6]] for more background information. | 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''' | '''Unknown Followup''' | ||
See [[SA1.7-QR6]] and [[SA1.7-QR6]] for more background information. In | See [[SA1.7-QR6]] and [[SA1.7-QR6]] for more background information. In Q11 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. These discussions are nearlt completed. | ||
'''Followup NGI Core Services availability''' | '''Followup NGI Core Services availability''' |
Revision as of 21:02, 30 January 2013
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
Grid Oversight
Followup upgrades of unsupported software There were quite a large number of sites that were still running glite-3.1 and glite-3.2 software that is no longer supported. Last quarter a campaign was started to make these sites upgrade their services that run this software. This campaign was continued this quarter. COD has requested RODs to issued GGUS tickets to these sites and is following this up.
ROD teams newsletter
This quarter we have published a ROD teams newsletter in Januaryr. The rationale behind the newsletter is descibed in the SA1.7-QR4 report.
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 Q11 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. These discussions are nearlt completed.
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.
OMB
We are busy developing a procedure to incorporate test resources into the EGI infrastructure and to identify possible changes to the operational tools.
EGI TF12
We have organised a session for ROD teams at EGI TF12 in Prague. There were 26 participants. Further we gave two presentations from COd in the Future of Ops session at EGI TF12.
COD F2F meeting
3. Issues and Mitigation
Issue Description | Mitigation Description |
---|---|