LCG Service Coordination Meeting

→ Europe/Zurich
28/S-029 (CERN)

28/S-029

CERN

35
Show room on map
Jamie Shiers
Description
LCGSCM

Internal meeting for host laboratory LCG service providers focussing on issues on a timescale of ~1 week to ~1 month.

Mailing list: lcg-service-coordination-meeting@cern.ch

Minutes
    • 10:00 → 10:20
      Outstanding Issues & Actions 20m
      • Experiment servers / services: status
        See CMS task force of Sep 20 and this wiki

        Also affects ATLAS "Tier1" VO boxes that are being setup / tested at CERN.

      • Cleaning of databases prior to multi-VO tests
        On several occasions, the database behind various services have needed to be "cleaned" to prevent performance degradation. This has applied to CASTOR DBs, FTS, dCache etc. Have all the necessary cleaning operations been performed at CERN and outside sites ready for the multi-VO throughput tests starting March 26th? Should these operations be performed regularly? Automatically?
      • Other changes in the pipeline
    • 10:20 → 10:40
      LCG Service Review 20m
      • <a href="https://twiki.cern.ch/twiki/bin/view/LCG/LcgScmStatusDeploy"> Certification/Pre-production </a>
        Highlights:
        Certification:
      • Progress of move to SL4 for all node types can be followed here: http://grid-deployment.web.cern.ch/grid-deployment//cgi-bin/reports.cgi?action=index

      • PPS:
      • SRM 2.2 testing started
      • ATLAS testing (certification) of DENY tag in VOViews started.
      • FTS 2.0 in the PPS
      • SL4 'interim' WN released to production
      Speakers: Nick Thackray, Oliver Keeble
  • <a href="https://twiki.cern.ch/twiki/bin/view/LCG/LcgScmStatusMLR">Monitoring, Logging & Reporting</a>
    Speakers: Ian Neilson, James Casey
  • Core Grid Services
    Speakers: Gavin McCance, Jan van Eldik, Thorsten Kleinwort, Ulrich Schwickerath
  • Fabric & Infrastructure Services
    Speakers: Maria Dimou, Maria Girone, Remi Mollon
  • Experiment Issues
    wiki page

    The primary purpose of this item is to bring up any (hopefully rare) issues that are in danger of becoming "hot" if not given attention.

    By definition, this must be used sparingly (i.e. not for every single problem seen by an experiment) and experience has shown that these issues should be raised in advance, e.g. the day before (or even earlier if possible...)

    Speaker: EIS Team
  • 10:40 → 10:45
    Any Other Business 5m