SA1 coordination meeting

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
      CREAM CEs: enabling alarms

      Today, 27 CREAM-CEs are OK, 9 are not (1 is in maintenance, so I’m not counting it).
      Three quarters of 36 is 27, so the quorum suggested by Malgorzata (CCOD) has been reached.
      Proposal to make all CREAM CE tests critical and raising alarms in production by next Monday.

    • 10:30 10:50
      Updated OAT deployment plan
      Plan
      Process descriptions
      slides
      text
    • 10:50 11:00
      EGEE baseline
      Table of client versions
      Table of service versions
    • 11:00 11:20
      GILDA

      Report from SCG, 30/10/2009

      Romain reported on the EGEE plans to integrate the Gilda training resources into the production infrastructure. There have been several e-mail threads on this. The issues were discussed earlier this week at the SA1 operations meeting. Romain reported that many concerns were raised about this and not just security-related ones.

      The security concerns include the fact that the Gilda CA does not have robust enough identity vetting procedures to be accredited by IGTF.
      Gilda has a separate VO which has been registered with EGEE and one suggested approach has been to leave Sites to decide to support the Gilda VO and to also trust the Gilda CA. The sites would then have to agree to take on any risks.

      SCG discussed the security issues at some length and concluded that:

      a. The risks are more complex than individual sites agreeing to take on the associated risks. Any risks associated with Gilda work running at EGEE production sites potentially threatens the whole infrastructure.

      b. SCG is very concerned that EGEE procedures have allowed the Gilda VO (which violates currently adopted security policies) to be officially registered. SCG recommends that the Gilda VO should not be registered with EGEE. Several NGIs handle training at the national level and already have a local training CA. Perhaps this would be the best model to follow?

      c. SCG strongly recommends that Gilda certificates should not be issued online without appropriate identity vetting of the applicant.

      d. The Gilda Portal should meet the requirements of the recently adopted VO Portal Policy.

      more information
    • 11:20 11:30
      site state flow: suspended/uncertified
      document
      pictures
    • 11:30 11:45
      Review of action list

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

    • 11:45 12:00
      AOB
      Issue in SAM to Nagios migration