Week of 210426

WLCG Operations Call details

  • For remote participation we use Zoom: https://cern.zoom.us/j/99591482961
    • The pass code is provided on the wlcg-operations list.
    • You can contact the wlcg-ops-coord-chairpeople list (at cern.ch) if you do not manage to subscribe.

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
  • 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

Monday

Attendance:

  • remote: Alberto (MONIT), Andrew P (NL-T1), Andrew (TRIUMF), Borja (Chair, MONIT), Christoph (CMS), Concezio (LHCb), Daniel (Security), David B (IN2P3), David M (FNAL), Doug (), Federico (LHCb), Francesco (), Julia (WLCG), Julian (Storage), Maarten (ALICE), Pepe (PIC), Peter (), Xavier (KIT)

Experiments round table:

  • ALICE
    • Occasional drops in activity last week due to Task Queue DB overloads.

Sites / Services round table:

  • ASGC: NC
  • BNL: NTR
  • CNAF: NTR
  • EGI: NC
  • FNAL: NTR
  • IN2P3: Mass storage system intervention ongoing.
  • JINR: NTR
  • KISTI: NC
  • KIT: On Friday we launched new dCache pools that provide the 2021 storage increase to our clients. However, it became apparent that the servers had issues when connections were done over IPv4 (GGUS:151516). We're still investigating. Meanwhile the new pools were excluded from production again.
  • NDGF: NC
  • NL-T1: NTR
  • NRC-KI: NC
  • OSG: NC
  • PIC: NTR
  • RAL: NTR
  • TRIUMF: NTR

  • CERN computing services:
    • Person in ROTA noticed an increase of user supporting tasks related to CMS and the job submission using VOMS

    • Luis: Nothing mayor, but would like to know if this is related to some specific activity happening or there is something we need to document/clarify better.
    • Christoph: Not aware of anything, but will try to clarify with my CMS colleagues.
  • CERN storage services: NTR
  • CERN databases: NC
  • GGUS:
    • A new release is planned for Wed this week
      • Release notes
      • A downtime has been scheduled for 07:00-09:00 UTC
      • Test alarms will be submitted as usual
  • Monitoring:
    • Got green light from CRIC for SiteMon migration (Thanks a lot for the efforts!)
      • We have requested experiment representatives to go for a last validation on the SiteMon data itself
      • If no any blockers change will be done on next Thursday 29th of April
  • Middleware: NTR
  • Networks: NTR
  • Security: Vulnerability in the Linux iSCSI driver. (CVE-2021-27363, CVE-2021-27364, CVE-2021-27365). Updates are available so please update your systems

AOB:

Edit | Attach | Watch | Print version | History: r14 < r13 < r12 < r11 < r10 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r14 - 2021-04-26 - NikolayVoytishin
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2024 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