SA1 coordination meeting

Name: SA1 coordination meeting
Start: 2009-10-20T10:00:00+02:00
End: 2009-10-20T13:00:00+02:00
Location: CERN

Tuesday 20 Oct 2009, 10:00 → 13:00 Europe/Zurich

28-R-06 (CERN)

28-R-06

CERN

Description

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

Actions, https://twiki.cern.ch/twiki/bin/view/EGEE/SA1_CoordinationTasks

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

The conference call opens 15 minutes before the meeting starts.

- 10:00 → 10:10
  Admin matters
  1. DSA1.4: Progress report on SLA implementation
  2. MSA1.10: Grid Computer Security Incident Handling
  3. DSA1.5: Operations Cookbook
- 10:10 → 10:30
  
  Requests for new ROCs
- from EELA, Canada, Mediterranean countries
- move from administrative/political/etc structure to a purely support structure
- definition of the functions and responsibilities
- do wee need to create a ROC only for profiting from SAM tests, GridStat and GridMap views?
- Introduction to new ROC_LA

10:30 → 10:40

Weekly operations meeting

10:40 → 11:00

EGEE service baseline list

being updated; we will soon start to monitor versions and to request to upgrade to supported version

policies to upgrade being defined, to exclude sites running very old versions

list of services to watch now: - scas, argus - CREAM - RBs, WMS 3.2

11:00 → 11:10

Feedback to EGEE League Tables

https://twiki.cern.ch/twiki/bin/view/EGEE/MonthlyAvailability

Still missing many reports from sites which didn’t meet the SLA target.

From the sites suspended as agreed at last meeting, one was set to "uncertified" and another one to "suspended" in GOCDB. What is the correct state?

From Gilles:

From a GOCDB point of view there is no enforcement of the succession of certification states, all transitions are technically possible. I am not sure about the political/operational aspect of the procedure, I would have thought this is in the operations manual?

My understanding would be that if a site is suspended then it should obviously be set to "suspended" in GOCDB, and become "uncertified" again when the ROC thinks the site is ready for re-entering the certification process.

However I would check it against the operations manual where this kind of certification status transitions should be stated.

11:10 → 11:30

GILDA sites in the production infrastructure

objective (from DoW): In the second year of the project, the resources within the current GILDA infrastructure will be integrated into the production infrastructure using the GILDA training VO that already exists on the training infrastructure. NGIs can of course enable their national training VOs on their resources and documentation will be provided to show how this can be done permanently or temporarily to support a specific training session. Central services (i.e. CA, BDII, GridWay, etc.) to access GILDA VO enabled production resources will continue to be run. Access to the resources used for training will be controlled so that sufficient capacity can be made available when required for the training courses. These resources will need to support the CA being used for the training course – generally the GILDA CA. New milestone MNA3.6 (PM19) will document the progress on this integration task.

status update from Gilda

requirement: all GILDA sites registered in the GOCDB, monitored by the same tools of the production infrastructure and a separate view on GridMap.

Security concerns

11:30 → 11:40

AOB

joint GAG/Ops portal Advisory Group:
Helene, Tiziana, John and Claire had a phone conference last week to discuss the formation of a joint Advisory Group for the GAG and Operations Portal. We have agreement in principal and a timeline in order to do this. It was decided that the place for technical discussions, milestones and dependencies is and will remain the OAT. The GAG is currently used for capturing customer requirements, prioritizing tasks and to announce future plans and releases which roughly coincides with the Operations Portal remit.
Most (but not all) stakeholders attending each group are the same people so it should be a good use of people’s time. We have some small issues to work on (such as deciding on a name, setting up mail lists, announcing the changes to stakeholders etc).
The GAG will hold a regular meeting in November. We then have plans for a joint meeting in December (teleconference) and a first face to face in January/February. Ideally this could run alongside the SA1 meeting, but if this is a problem Helene is able to host the meeting in Lyon.

Reminder of QR6

dates and location for next F2F SA1 coordination meeting

OAT update at next meeting