EGI-InSPIRE:SA1.7-QR13

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


Contents


1. Task Meetings

Date (dd/mm/yyyy) Url Indico Agenda Title Outcome
June 6th 2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1715 COD phone conf https://indico.egi.eu/indico/getFile.py/access?resId=0&materialId=minutes&confId=1715

2. Main Achievements

Grid Oversight

Followup upgrades of unsupported software

COD is involved in the process of retirement the EMI-1 middleware. The majority of services were already upgraded. Currently COD oversights process of StoRM service retirement (7 instances). In near future the EMI-1 dCache service withdrawal, that has extended support till 31.08.2013, will be performed.

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 Q13 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 nearly 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. This activity has been continued in this quarter.

Nagios Probe working group

SAM/nagios probe WG finished dealing with EMI-1 probes integration issues. A final issue of dropping org.arc.AUTH and org.arc.SW-VERSION metrics was noticed and agreed with NGIs. The next step is to select the probes which should be turned operations, but this will be done when SAM update 22 is deployed by majority of NGIs.

The WG is currently dealing with the following new requests:

* revise SE probes (alarms for VO for low free space available) 
* probe development requests from VOs
* too much resources requested by new MPI probes

Software support

The activity ran smoothly following the established procedures. Number of tickets handled in this period is lower (125 vs. 173 and 192 in preceeding quarters), which is an expected drop in the main vacation period. The ratio of solved tickets is 24% which remains within the usual range (20-30%).

This is the first reporting period after the end of EMI and IGE projects. However, due to thorough preparation and establishment of support relationships with the individual product teams no particular issues were encountered.

In July a proposal for 2nd level software support EGI core tasks was submitted to the bid for the post-InSPIRE period. Out of the current project partners contributing to this task, CESNET, STFC and JUELICH participate formally in the bid, while INFN and NDGF promise informal best-effort support.

3. Issues and Mitigation

Issue Description Mitigation Description
Grid Oversight: None

4. Plans for the next period

Grid Oversight

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 we will make further progress on this.

Further plans

We will continue the activities that we already doing. Further we are going to proceed with carrying out the plan outlined in https://indico.egi.eu/indico/getFile.py/access?contribId=4&resId=0&materialId=slides&confId=1100 and startup the plans described in https://documents.egi.eu/public/ShowDocument?docid=1529. 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.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export