CTA operations

Wednesday 28 Jan 2026, 10:30 → 11:45 Europe/Zurich

513/R-068 (CERN)

Julien Leduc (CERN)

This meetings covers EOSCTA service operations at CERN: minutes, community

 

Rota

• 20260121-20260128
• CERN Digital Memory project on CTA
  • Another round of reconfiguration... and this is not yet final
• 1/3 of ALICE archives are finished (~15PB)

Tape infrastructure

• Tape supply specifications for tape operations
• Work in progress: converge toward what the current supply duty is/is not
• 3 BROKEN 3592JC7T tapes
• Namespace dump being generated communicated to ATLAS when available

Use cases

• Operator create an operations ticket with label "needs dev issue"
• when Creating dev ticket: status:blocked label: workflow:awaiting release and link dev ticket as blocked by.
• if workaround is needed and implemented in production add label workaround in production and states what was done/link in ticket description
• for example supply column size not sufficient
• Error message missing when changing media type of non-empty tape
• Missing error for operators and inconsistent frontend log entry
• 2026-01-24: ctaproductionfrontend11 oomkilled multiple time over a single week end
• oomkill is not good enough we should configure a maximum amount of memory our processes are allowed to consume
• Additional protections on ctaproductionfrontend physics endpoint
• Avoid accidentally running operations commands on the main physics endpoint as these can lead to additional memory consumed and affect production
• Strict isolation between physics endpoints and operations frontend should be the target
• Features needed in production for 2026 run restart
• cta 5.11.16 and 5.11.17 in the pipelines
• see YETS-2025 issues awaiting release

AOBs

• https://gitlab.cern.ch/cta/CTA/-/issues/1505