Week of 190729

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: Alberto (Monitoring), Borja (Chair, Monitoring), Ivan (ATLAS), Julia (WLCG), Maarten (ALICE), Renato (LHCb), Vincent (Security)
  • remote: Brian (RAL), Christoph (CMS), Dave (FNAL), Di (TRIUMF), Marcelo (CNAF), Onno (NL-T1), Xavier (KIT)

Experiments round table:

  • ALICE -
    • NTR

  • LHCb reports ( raw view) -
    • Activity:
      • MC, user jobs and staging.
      • Important to have all sites with split aliases otherwise need to maintain an hack in the code. Still missing SARA (split is difficult form their side).
    • Issues:

Sites / Services round table:

  • ASGC: NC
  • BNL: NC
  • EGI: NC
  • FNAL: Some user connections using IPv6
  • IN2P3:
  • JINR:
    • Our networking experts still working on ticket GGUS:141833.
    • We submitted another ticket for this problem in GGUS GGUS:141954.
  • KIT:
    • On Thursday, 25th of July, the updates to one of our core routers went wrong and many of our WNs briefly lost their connectivity. Later the same day, public interfaces for many other machines were not reachable for a couple of minutes. All of that was covered by the at-risk downtime in GOCDB:27503. Because we've had that many issues, we postponed the update for our second core router for now.
    • Nearline storage will be offline for all VOs the last two weeks of September (GOCDB:27529 (LHCb), GOCDB:27530 (ATLAS and CMS)). We need to clean inside the libraries and all tape cartridges in order to reduce the wearing.
    • In the same time frame, probably Tuesday and Wednesday, 17th/18th of September, we want to update our shared GPFS cluster version, so all online storage will be down.
    • Additionally, we're looking for other maintenance tasks that require a site downtime to further exploit the occasion.

Maarten did ask why ALICE was not in the list, Xavier replied ALICE is not available in GOCDB, thus he can't include a downtime there.

ATLAS had further questions offline on why it was declared as an outage for LHCb but as a warning for ATLAS+CMS, here is the answer from Xavier:

"The nearline storage will be offline for everyone, including ATLAS. The reason why we didnít announce an outage is, that the online storage will be available to you throughout the whole time. In case of LHCb, we have two SRM endpoints in GOCDB, one about the online and the second about the nearline part of the SE, even though the actual SRM endpoint is the very same one. So we declared the outage just for the nearline SRM service."

  • NDGF: NC
  • NL-T1: NTR
  • NRC-KI: NC
  • OSG: NC
  • PIC: NC
  • RAL: NTR
  • TRIUMF: There will be a 4-hour downtime scheduled on Monday to upgrade dCache to 4.2 and its Postgres DB, we will also reboot all the WNs for new kernel in the downtime.

Julias asked about the version chosen to upgrade, since the currently considered "golden" version is 5.2. Di replied they wanted to update to a closer stable version first to avoid unexpected problems. Update to 5.2 will be considered in the future.

  • CERN computing services: NTR
  • CERN storage services: NC
  • CERN databases: NC
  • GGUS:
    • A new release is planned for Wed this week
      • Release notes
      • A downtime of a few hours will be scheduled for Wed morning CEST
      • Test alarms will be submitted as usual
  • Monitoring: NTR
  • MW Officer: NC
  • Networks: NTR
  • Security: EGI sent a 'HIGH' advisory last week (details in that mail)


Edit | Attach | Watch | Print version | History: r17 < r16 < r15 < r14 < r13 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r17 - 2019-07-31 - 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-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