Week of 190121

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: Alberto (Monitoring), Borja (Chair, Monitoring), Gavin (Computing), Karolina (Databases), Renato (LHCb), Miroslav (Databases), Petr (ATLAS), Remi (Storage), Vincent (Security)
  • remote: Darren, Dave (FNAL), David B (IN2P3), Di (TRIUMF), Jens (NDGF), Xavier (KIT), Marcelo (CNAF), Onno (NL-T1), Stephan (CMS)

Experiments round table:

Asked by ATLAS whether REBUS (which hasn't been updated since April last year) is still used for the old monitoring tools and what are the plans. It was agreed to contact the experts and come back with an answer.

  • CMS reports ( raw view) -
    • No major grid computing issue(s)
    • Running smoothly at about 200k cores
      • 75% production, 25% analysis

  • ALICE -
    • Normal to high activity on average
      • A central service issue caused a drop as of ~04:00 CET today
      • Job numbers are increasing again as of ~10:00 CET

  • LHCb reports ( raw view) -
    • Activity
      • Data reconstruction for 2018 data
      • User and MC jobs
    • Site Issues
      • CERN : NRT
      • Tier-1s : NTR

Sites / Services round table:

  • ASGC: NC
  • BNL: Just a reminder --- tomorrow (01/22) BNL ATLAS T1 scheduled downtime, dCache upgrade.
  • CNAF: NTR
  • EGI: NC
  • FNAL: NTR
  • IN2P3: NTR
  • JINR: NTR
  • KISTI:
  • KIT:
    • Last week's downtime on Wed went fine and was closed after 25 minutes. Though unexpected issues surfaced shortly after and we had to enter a new unscheduled downtime for 10 minutes. Since then, everything seems fine.
  • NDGF:
    • There will be a dCache pool upgrade tomorrow, during the downtime some ATLAS and ALICE data will be unavailable.
  • NL-T1: NTR
  • NRC-KI: NC
  • OSG: NC
  • PIC: NC
  • RAL: NTR
  • TRIUMF: NTR

  • CERN computing services:
    • OTG:0047775: The legacy lcg-voms2.cern.ch service will be decommissioned on 4 March 2019. Any VOMS client configurations still using the legacy service should be reconfigured to use the voms2.cern.ch service.
      • Ops Coordination will send broadcasts with instructions
    • OTG:0046088: LSF public deco, Wednesday 30th January 2019. (Dedicated shares handled separately.)
    • OTG:0047300: Draining HTCondor public now for CC7 upgrades. Schedule:
      • ce511, ce512, ce513, ce514 will be changed to submit to CC7 by the end of the month - there will be a specific OTG for this soon.
      • end January 2019: 30% public/grid will be CC7
      • end March 2019: 50% public/grid will be CC7
      • 2nd April 2019: lxplus.cern.ch alias change to CC7 (lxplus6 service will remain accessible on lxplus6.cern.ch), Default HTCondor target change to CC7 for local submission.
      • early June 2019: remainder of capacity will have ben migrated.
      • (Dedicated shares handled separately.)

Asked by Renato (LHCb) how the migration batchs are planned in order to understand better whether jobs will be running in both OS depending where they are submitted. Answer is it will depend on the submission nodes used.

  • CERN storage services:
    • FTS: FTS ATLAS instance planned to be upgrade to FTS 3.8.2 on Tue 22 Jan from 9:30 tp 12:30 CET (OTG:0047788)
  • CERN databases:
    • Transparent upgrade of production database storage on Tuesday 22nd Jan.
  • GGUS: NTR
  • Monitoring:
    • December 2018 final reports sent around
  • MW Officer:
  • Networks: CERN: LHCOPN router migrations for PIC, TRIUMF, KISTI, ASGC today from 4pm (OTG:0047779, OTG:0047869, OTG:0047866, OTG:0047865)
  • Security: NTR

AOB:

Edit | Attach | Watch | Print version | History: r22 < r21 < r20 < r19 < r18 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r22 - 2019-02-15 - 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