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

    LCG Service Coordination Meeting

    → Europe/Zurich
    513/1-024 (CERN)

    513/1-024

    CERN

    50
    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
        • Reinstallation of service nodes - target end 2006
        • Experiment servers / services: status
          See CMS task force of Sep 20 and this wiki
        • prod-lfc-atlas-central.cern.ch - status and plans
          The so called "central" lfc is prod-lfc-atlas-central.cern.ch. It is not used by the ATLAS DDM but unfortunately has a legacy role for the users.

          Q: when can we shut it down? 31st April 2007?

        • CASTOR interventions - update on scope & schedule
          This should cover not only the Western Digital interventions, but also the various - many other things coming along:

          • Pending moves to new h/w of the various CASTOR components
          • Upgrade of CASTOR s/w components
          • etc.

          All these things have to be scheduled in / around the expeirments' FDR preparations and on-going productions

        • 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?
        • Service Resilience to "glitches"
          How robust are the current services to short-term "glitches" (longer term outtages is a separate but needed discussion...)

          Examples include:

          • Power glitch - all machines protected up to 10' (the definition of a "glitch" (A fault or defect in a system or machine)?)
          • Rolling upgrade / loss of contact to DB backend
          • OS patch / upgrade
          • m/w patch / upgrade

          More major interruptions - such as loss of network switch / non-rolling DB upgrade - need also to be considered and where possible protected against.

          H/W upgrades / moves -> rolling where possible?

        • Oracle Critical Patch Update
          Critical Patch Updates - see Release Schedule

          Starting 2005, Critical Patch Updates are the primary means of releasing security fixes for Oracle products. They are released on the Tuesday closest to the 15th day of January, April, July and October. The next four dates are:

          • 17 April 2007
          • 17 July 2007
          • (16 October 2007)
          • 15 January 2008
        • Other changes in the pipeline
        • Status of Service Intervention Assistant
      • 10:20 → 10:40
        LCG Service Review 20m
        • <a href=
          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
        • WLCG RAC Weekly Report 15m
          document