From EGIWiki
(Redirected from SA1.7-QR14)
Jump to: navigation, search
EGI Inspire Main page

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

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.

Review of certification procedures etc We are busy developing a procedure to incorporate test resources into the EGI infrastructure, review the certification procedures and to identify possible changes to the operational tools. This discussion is now finished and everything is handle by GOCdb5.

Software support

The task runs smoothly along the procedures established in past. In the reporting period 99 tickets were handled. The number is lower compared to preceeding periods even if the influence of main vacation season is excluded. It is likely to indicate that the software is getting more stable after the end of EMI and IGE projects, when the pace of development slowed down.

Out of those tickets 34% were solved by the software support, which is considerably higher ratio than before.

The organization of 1st and 2nd line software support during the project extension and afterwards was discussed again. A preliminary agreement on splitting the responsibility was reached with IberGrid which submitted a bid in first round too.

3. Issues and Mitigation

Issue Description Mitigation Description

4. Plans for the next period

We will continue the activities that we already doing. Further we are going to proceed with carrying out the plan outlined in and startup the plans described in More specific, this quarter we have stopped the followup of the top-BDII and RPI follow-up as a part of these plans. we will monitor the impact of this.