Week of 200302

WLCG Operations Call details

  • For remote participation we use the Vidyo system. Instructions can be found here.

General Information

  • The purpose of the meeting is:
    • to report significant operational issues (i.e. issues which can or did degrade experiment or site operations) which are ongoing or were resolved after the previous meeting;
    • to announce or schedule interventions at Tier-1 sites;
    • to inform about recent or upcoming changes in the experiment activities or systems having a visible impact on sites;
    • to provide important news about the middleware;
    • to communicate any other information considered interesting for WLCG operations.
  • The meeting should run from 15:00 Geneva time until 15:20, exceptionally to 15:30.
  • The SCOD rota for the next few weeks is at ScodRota
  • General information about the WLCG Service can be accessed from the Operations Portal
  • Whenever a particular topic needs to be discussed at the operations meeting requiring information from sites or experiments, it is highly recommended to announce it by email to wlcg-scod@cernSPAMNOTNOSPAMPLEASE.ch to allow the SCOD to make sure that the relevant parties have the time to collect the required information, or invite the right people at the meeting.

Best practices for scheduled downtimes



  • local: Andrei (DB), Borja (Chair, MONIT), Cristi (Storage), Ivan (ATLAS), Julia (WLCG), Maarten (ALICE), Vincent (Security)
  • remote: Andrew (TRIUMF), Concezio (LHCb), Darren (RAL), Dave (FNAL), Elena (CNAF), Jens (NDGF), Xin (BNL)

Experiments round table:

  • ALICE -
    • NTR

  • LHCb reports ( raw view) -
    • staging 2017 data from tape
    • stripping productions recovered from Feb 20th incident
    • considering a scheduled DT of DIRAC service in view of Oracle outage of next week ( OTG:0054761)

Sites / Services round table:

  • ASGC: NC
  • BNL: NTR
  • EGI: NC
  • FNAL:
    • Incident on Thursday caused by a range of IPV6 addressed not correctly registered, situation was fixed.
  • IN2P3: NC
  • KIT: NTR
  • NL-T1:
    • No-one available to dial in.
    • During today's downtime, Surfsara upgraded dCache to 6.0.9. The downtime completed successfully. The original downtime was longer (5 days), to include network maintenance, but that had to be postponed because new equipment could not be delivered in time.
  • NRC-KI: NC
  • OSG: NC
  • PIC: On 16th March we will be in SD (to be announced in GOCDB soon), for an update on dCache and HTCondor services.
  • RAL: NTR

  • CERN computing services: NC
  • CERN storage services:
    • There will be a presentation on WLCG ops/coord meeting about the CEPH outage
    • OTG:0055183: EOSALICEDAQ - software update
  • CERN databases:
    • Oracle and Database on Demand databases will be unavailable on the 11th of March in the morning, due to a network intervention
      • ACCLOG/ACCMEAS databases down due to network intervention OTG0054762
      • DBoD instances down due to network intervention OTG0054760
      • Oracle databases unavailable due to network intervention OTG0054761
      • Some clarification about the time things will be done was asked by Security and LHCb:
        • Oracle won't be accessible for few minutes
        • InfluxDB won't be accessible for around one hour
        • An email will be sent to wlcg operations services mailing list to raise the awareness, please check the linked OTGs

  • Monitoring:
    • Fixed issue with T2-Nebraska not appearing in the WLCG reports
    • Draft availability reports for February 2020 sent around
  • MW Officer:
  • Networks: NTR
  • Security: Security broadcast sent today to site, please check the content!


This topic: LCG > WebHome > WLCGCommonComputingReadinessChallenges > WLCGOperationsMeetings > WLCGOpsMeetingWeek200302
Topic revision: r17 - 2020-03-02 - JosepFlix
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback