The conference call opens 15 minutes before the meeting starts.
Recording of the meeting
10:00
→
10:10
Admin matters
MSA1.7
Next EGEE III all activity meeting: to discuss the transition over two days, starting Tuesday 27th January 2009 noon and ending Wednesday 28th January noon, in Brussels
The manpower issue raised last quarter was solved by reducing the scope of the COD pole2 mandate. In addition three people joined in to contribute to update and restructure the operational procedures. This Pole 2 is now coordinated by the SEE ROC, in replacement of DE-CH which left in July. This coordination will be a joint effort with the new people joining.
During this quarter, the site representatives initiated four requests for input to site managers, via EGEE Broadcast. Due to the lack of input coming from the sites, the site representatives “represented” the sites to the best of their technical ability in the EGEE Technical Management board. We are open to suggestions on how to get better response from the sites.
In the light of the recent developments in GGUS concerning direct ticket routing and also planning ahead into the EGI era, the role of the TPM has to be reconsidered. Also the role of the regional help desks in the distributed operations model needs to be evaluated. This will be done through the periodic user support activities in close collaboration with the rest of SA1.
Although MSA1.5 states that no specific implementation is necessary for the tracking of monthly SLA conformance, it is generally felt that there is a need for some form of SLA Portal. The OAT (Operations Automation Team) is collecting the requirements, but the current EGEE DoW does not include resources for the implementation.
MSA1.5 states that the SLA Working Group will be continued in EGEE-III, with each ROC supplying a person. No names have been volunteered as of the time of writing, but the SLAG is meant to be formed in October (M6).
The issue mentioned in the last quarter about JRA1 members reacting only to items submitted to the Savannah bug tracker and not to tickets submitted to the GGUS system is being extensively discussed between SA1 and JRA1 and we are close to find a solution.
The main issue the UKI ROC has faced during Q2 is recruitment of new EGEE staff due to late signing of the GA and delays this caused the in preparing and signing the local agreement. STFC is distributing EGEE advance payments quarterly in advance to its JRU partners and the delay in the ICC PPT tool is delaying their payment, because we base forward payments on previous cost claims. Also members do not appear to be getting timesheet reminders causing timsheets submissions to be delayed.
For some production sites there were some issues in this reporting period caused by the deployment of certain gLite updates which were not properly verified, and despite that have been put into production. For clients, such problems are avoided testing all updates locally before installing them in production at the site (regional/site certification). With other services (e.g. CE, SE, VOMS etc.) some small sites take the approach of waiting several days to see if problems are reported on common lists or through EGEE broadcasts, and only then they proceed. This introduces some delays to deploy new released versions into production. SA1 will discuss in the next quarter how this could be solved, mainly by building on the informal process already started by some sites.
10:30
→
10:45
metrics from QR2
There are some metrics that deserve a detailed analysis to understand where we are, as they change the trend from the last months:
