SA1 coordination meeting

Tuesday 12 Aug 2008, 10:00 → 12:00 Europe/Zurich

28-R-06 (CERN)

Minutes, https://edms.cern.ch/document/923879

Actions, https://edms.cern.ch/document/923881

This meeting is 10:00 to 11:30 UTC+2
Phone number is: +41 22 767 6000
Access code is: 0181908
Or click here: https://audioconf.cern.ch/call/0181908

The conference call opens 15 minutes before the meeting starts.

The rota for taking the minutes can be found here: ROTA . Please note that the minute taker must also update the action list!!

For this meeting, it is the turn of the RUSSIAN ROC to take the minutes.

Recording of the meeting SA1_Coord_Meeting_2008-08-12.wav

10:00 → 10:10 Admin matters

1. DSA1.1 Plan for continued development of GGUS: PEB approved
2. MSA1.1 Operations Automation Strategy - PEB approved; distributed to external reviewers
3. MSA1.2 Operations Procedures in Use: pending change on references link
4. MSA1.3 Activity QA & Measurement plan:
5. MSA1.4 Security Assessment Plan:
6. MSA1.5 SLA Roadmap: ongoing

10:10 → 10:25 Partner reviews

EGEE federation reviews


https://edms.cern.ch/document/905673/1


SA1 partner reviews: proposal to replace them by periodic reports from partners, sincronized with QR times.

1. How to get input from each partner: proposal to get report from each partner reporting progress against the **subtasks** they committed to at the WBS. Each JRU lead beneficiary should get the input form the other JRU partners and send it all together to the ROC managers list so the activity manager and the task responsibles can read it. Dates: next input required by mid-October.

10:25 → 10:45 Recommendations from EU review

1. SA1. Leverage user requirements at sites as a means to encourage site administrators to improve
   infrastructure reliability and to implement the available gLite features more fully at those
   sites.
2. SA1. Ensure that support procedures (including helpdesk operation, ticketing procedure, escalation
   and de-escalation) are as transparent as possible.
3. SA1. Document best practices in support so that they can be fully exploited.
4. SA1. The overheads on becoming a grid user should be kept as low as possible, to encourage
   smaller and less traditional user communities. Processes (e.g. resource allocation) should be
   transparent and efficient, to make it easier for users to report problems and request improvements.

10:45 → 10:55 issues raised for QR:

1. Issues that came out of the COD 16 meeting have been raised to the SA1 coordination meeting of July 10th. It comes down to an under-involvement in extra-Rota activities of some federations in EGEE-III. Namely, Pole2 is understaffed. Requests at the COD-16, requests to the federations already coordinating, and a report that was done at SA1 coordination meeting could not raise enough involvement so far. Without any new strategy, we will adopt a streamlined mandate, and we will provide best effort on a minimal scope e.g. focus on the restructuring of Operations Manual Procedure.
2. OSCT: little contributions from the following ROCs, compared to the expected efforts from them.
   - France (24 PM): A new member joined, but she has little security expertise and significant difficulties to communicate in English
   - Dech (24 PM): they are still trying to employ someone
   - Russia (12 PM): the contact rarely attends the phone meetings and is busy with other activities. It is a shame, as he is knowledgeable.
   

10:55 → 11:05 AOB

1. This is an outcome of the GOCDB advisory group that needs validation from the ROC managers before implementation into the GOCDB development list. Savannah bug 1064651 ======= to be validated by ROCs Use-Case: Broadcasts or downtime notifications trigger tickets in some local helpdesks Rationale: Some site contacts defined in the GOCDB are pointing to local helpdesks Proposed Solution: Add a fourth field to the existing 3 ones in Site ID cards in the GOC DB : "contact e-mail", "security e-mail", "emergency e-mail" -- GGUS sends mails to this contact in case of security alerts. Fourth field definition: "support e-mail" : -- mail of contact of local helpdesk that could trigger tickets within, set to contact e-mail by default. Important Remark and line of reasonning: Broadcast, Reminders and Downtime Notifications would still point to site contact only . Adding this specific field would drive sites and ROC to differentiate the 2 "contact e-mail" and "support e-mail" and fill in the new e-mail appropriately if they want to avoid the aforementionned use-case. ===============Savannah bug 1064651