Rucio Meeting

Thursday 12 Dec 2024, 15:00 → 16:00 Europe/Zurich

Martin Barisits (CERN)

15:00 → 15:05 News

• Next week
  • Rucio 37 "Dungeons & Donkeys" release roadmap planning
  • Last meeting of the year!
    • Next meeting on 9 January 2025
• Rucio 36 CLI
  • Two major changes: new command structure and use of Rich (opt-in)
    • Please notify your communities!
    • Please test and report issues
      • #7224 and #7225 will be used to track the progress.

15:05 → 15:25 Community News & DevOps roundtable

• ATLAS
• CMS
  • Q: source-selection algorithm, tapes, and multi-hop transfers
    • Do we need some recommendations on the distance values and the penalty?
• Fermilab DUNE/RUBIN/etc
  • Will use multi-hop for CERN, FNAL, and IN2P3 tape
  • Now running Rucio 35.6.0 everywhere
  • Working on deploying the Conveyor Receiver
    • In talks with CERN to consume the messages
• DUNE
  • Looking for instructions on how to enable tokens in parallel to X.509
  • CILogon: good progress on the Rucio and FTS test scripts
• DaFab
• HEPCCE
  • Some difficulties launcing a development environment
    • To start working on Globus Online support

15:25 → 15:45 Rucio 36 release retrospective

Speaker: Martin Barisits (CERN)

Retrospective board

• Items from 35 release retrospective
  • Plan a documentation hackathon ✅
  • Documentation corner: Make it mandatory to add 1-2 items per release roadmap ✅
  • Investigate documentation on configuration of tape storage elements: e.g. srm vs other protocols, archive timeout, copy_pin_lifetime, bring_online, etc. - Just more detail in how to handle tape RSEs
    • Ongoing in DocuSprint24
  • Improve CI testing framework (Be able to run GH actions locally?)
  • Test coverage, test quality ✅
  • More support for cloud RSES and cost control ✅
  • Evolve the roadmap mechanism (sprints…)
    • Planned for 37 release
  • Investigate how to propagate information on deprecation of certain modules/functionality (e.g. C3PO, OIDC modules, etc.)

15:45 → 15:55 Developers roundtable

• (Riccardo): long-term, should we only allow Rich CLI?
  • Release 36: Rich is an opt-in
  • Release 37: Rich is an opt-out
  • Release 38: tabulate is removed and Rich is the only available method
• Docusprint finishing tomorrow

15:55 → 16:00 AOB