Week of 200615

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
  • 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:
  • remote: Andrew (NL-T1), Andrew (TRIUMF), Borja (Chair, Monitoring), Darren (RAL), Dave (FNAL), David (IN2P3), Ivan (ATLAS), Julia (WLCG), Luis (Computing), Maarten (ALICE), Vladimir (LHCb)

Experiments round table:

  • ATLAS reports ( raw view) -
    • Software and Computing Week
    • ARC6 migration. Set sites disabled on end of July? EGI tickets (Example). It should not be enforced.
      • We do not want sites to be turned off in the middle of summer.

  • Ivan: Would it be possible to avoid having this deadline in the middle of summer?
  • Maarten: We will check with EGi the timing for these decisions. Anyhow non production doesn't mean the site can't be used (at the user own risk)

  • CMS reports ( raw view) -
    • It's (virtual) CMS Week and likely nobody from CMS can call in
    • Nevertheless no major issues to report

  • ALICE -
    • NTR

  • LHCb reports ( raw view) -
    • Activity:
      • Usual MC, user and WG production.
    • Issues:
      • CERN: DATA transfer problem GGUS:147426 (fixed)
      • FZK-LCG2: CE unavailable GGUS:147431 (fixed)
      • RAL: low number of running jobs

  • Vladimir: Is there a way to make sure GGUS tickets are marked as resolved when they are?
  • Maarten: We can remind sites in operations (coordination) meetings, but this is something that can happen from time to time
  • Borja: Could LHCb ping in the tickets to double check they are resolved?

Sites / Services round table:

  • ASGC: NC
  • BNL: NC
  • CNAF: NC
  • EGI: NC
  • FNAL:

  • Julia: We sent you a request for validation of some accounting information
  • David: Yes, we will take care

  • IN2P3: IN2P3-CC will be in downtime tomorrow. CEs and SEs will be off. CREAM-CEs will be decommissioned.
  • JINR: NTR
  • KISTI: NC
  • KIT:
    • All trouble with the CMS dCache database (GGUS:146951) should now be understood and resolved.
    • IPv6 connectivity issues between KIT and MWT2 (GGUS:147325) went away without changing anything on our side.
    • BDII endpoint on arc-5-kit.gridka.de was down (GGUS:147431), now fixed.
    • Service certificate for use by DIRAC on the LHCb vobox (GGUS:146959) still not perfect.
    • Downtime for updating software on two of our border routers tomorrow from 9 to 12 o'clock CEST (GOCDB:28935)
  • NDGF: NC
  • NL-T1:
    • The Sara dCache has been downgraded from 6.1 to 6.0.16 to fix instabilities. Things look much better now, except for directory listings, these are very slow. This is being investigated.
  • NRC-KI: NC
  • OSG: NC
  • PIC: My excuses, I cannot connect today. Tomorrow Tue. 16th June, in the morning, we have a declared SD downtime to upgrade Enstore at PIC.
  • RAL: NTR
  • TRIUMF: NTR

  • CERN computing services:
    • The Batch Service is working on a new offering of pre-emptible capacity on opportunistic resources for grid workloads. These resources will come from different sources: OpenStack pre-emptible VMs and Azure SpotVMs.
      • Jobs running on these resources can be pre-empted without any grace period.
      • Further details will be given when the new route is available in the CEs, but if you're interested on this service, please get in touch for early testing.
  • CERN storage services: NTR
  • CERN databases: NC
  • GGUS: NTR
  • Monitoring: NTR
  • MW Officer: NC
  • Networks: NTR
  • Security: NTR

AOB:

Edit | Attach | Watch | Print version | History: r18 < r17 < r16 < r15 < r14 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r18 - 2020-06-15 - MaartenLitmaath
 
    • 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-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback