Go to the Indico Home Page Oldest event Older event Up to category Newer event Newest event Printable version
  • Compact style
  • Indico style
  • Indico style - inline minutes
  • Indico style - numbered
  • Indico style - numbered + minutes
  • Indico Weeks View
    • Switch to the management area of this event
    Login

    SA1 coordination meeting

    → Europe/Zurich
    28-R-06 (CERN)

    28-R-06

    CERN
    Description

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

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

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

    The conference call opens 5 minutes before the meeting starts.

    The rota for taking the minutes can be found here: ROTA

    For this meeting, it is the turn of the UKI ROC to take the minutes.
    Recording of the meeting
      • 10:00 → 10:30
        Operations Automation Team 30m
        1. Update and summary of last meetings
        2. MSA1.1: Operations Automation Strategy
        Speaker: James Casey (CERN)
        Paper
      • 10:30 → 11:00
        COD mandate 30m
        MANDATE:
        1. Move from central COD model to regional COD model; goal: central COD as we understand it today does not exist at the end of EGEE III; all rocs running a regional cod by the end of egee III
        2. Define what a “thin central COD layer” would do, and if needed introduce it in the new COD model
        3. Coordination between regional CODs and central thin layer COD (if needed)
        4. Communication and share of expertise between regional CODs
        5. Update and maintain common operational procedures

        MAIN CONCERNS (extracted from Helene's presentation at the transition meeting):
        1. Follow-up on the requirements on each of the monitoring tools for COD daily work and tools integration purposes
        2. Process failover of all operational tools needed for COD work
        3. Assessment of the operational tools availability
        4. Need to define the interface with OAT, ROCs
        5. Make the COD structure evolve to gather and coordinate manpower to improve and enhance COD service now and in transition phase to regional model
        6. COD mandate need to be officially agreed on, for federations to foresee the manpower at the same time as the OAT
        7. Community building for the two following purposes:
          1. 1rst line support generalization and consequences on tools and procedures including set-up of a knowledge base
          2. Experimentation on what the operations model of the next COD generation in EGI could be
        8. Need of interface to OAT in terms of requirements follow-up : Monitoring tools, failover, integration tool (The OAT handles development and availability of monitoring tools. CODs (r-CODs, c-COD), as users of those tools, are clients of the OAT. They assess their reliability.)
        9. Need of interface to ROC via internal committees : ROC-Forum for setting-up failover mechanisms for m/w core services
        Speaker: Helene Cordier (CNRS/IN2P3)
        more information
      • 11:00 → 11:15
        MSA1.2: Operations procedures in place 15m
        Responsible: CNRS
        Description: This milestone updates the set of procedures for operating the EGEE infrastructure. It includes the grid operations procedures, operational security and user support procedures.
        Speaker: Rolf Rumler (IN2P3-CC)
      • 11:15 → 11:35
        AOB 20m
        1. requirements for seed resources
        2. SAM test for APEL: request (via the ROCs) to have all sites associate the newly-created APEL service in GOCDB to one of their CEs.
        3. Call for volunteers for PPS pilot service of Cream CE