From EGIWiki
(Redirected from SA1.7-QR16)
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

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.

Software support

In Q16 software support received 86 tickets, which is lower number compared to previous periods, indicating that the set of deployed components is in more stable state at the end of the project. Out of those 22 were solved at the 2nd level, which is withing the range of usual ratio.

Organizational work was targeted to the new support model in the upcoming months. The procedures were agreed, the 1st level will follow weekly shifts alternating between CESNET and Ibergrid. At the CESNET side the shifts are integrated into the work of its general helpdesk.

The list of supported software components at the 2nd level was revised and assignments to both CESNET and Ibergrid, and other unfunded contributing partners (in case of the community platform) were done.

The new work model was deployed in advance in April, no major problems appeared.

3. Issues and Mitigation

Issue Description Mitigation Description

4. Plans for the next period

Handover the work to Miss M.