Week of 180625

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

Monday

Attendance:

  • local: Alexey (LHCB), Borja (Chair, Monit), Gavin (computing), Maarten (ALICE), Miroslav P (DB), Remi (Storage)
  • remote: Andrew (NL-T1), Christian (NDGF), Dave M (FNAL), Sang Un (KISTI)

Experiments round table:

  • ATLAS reports ( raw view) -
    • ATLAS Software and Computing Week in Hamburg (25.06 - 29.06).
    • Probably no one will be able to connect.

  • CMS reports ( raw view) -
    • It is CMS week, not sure we will be able to connect
    • A calm week: no data taking, distributed computing at 220+50 k Cores (prod + analysis)
    • Only central feature to report is the persistent problem in FTS monitoring in KIBANA (RQF:1045551)
    • We are still trying to understand where is the limit in writing to CERN tape (currently 1.6 GB/s). If it turns out to be in the infrastructure, we will contact CERN/IT. At the moment we cannot exclude it is on our side.

  • ALICE -
    • NTR

  • LHCb reports ( raw view) -
    • Data reconstruction for 2018 data, MC simulation, user jobs

Sites / Services round table:

  • ASGC: nc
  • BNL: nc
  • CNAF: nc
  • EGI: nc
  • FNAL: NTR
  • IN2P3: nc
  • JINR: nc
  • KISTI: NTR
  • KIT: nc
  • NDGF: NTR
  • NL-T1: NTR
  • NRC-KI: nc
  • OSG: nc
  • PIC: nc
  • RAL: NTR
  • TRIUMF: In the process of migrating some grid services to new data centre. Only decommission old services when the new services are working fine, so no downtime is needed at the moment.

  • CERN computing services: NTR
  • CERN storage services: NTR
  • CERN databases: NTR
  • GGUS: NTR
  • Monitoring: NTR
  • MW Officer: NTR
  • Networks: NTR
  • Security: NTR

AOB:

Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r11 - 2018-06-25 - BorjaGarridoBear
 
    • 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-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback