Focus on:  Hide Contributions
Login

BiLD-Dev

→ Europe/Zurich
2/R-014 (CERN)

2/R-014

CERN

10
Show room on map
Federico Stagni (CERN)
Description

Bi-Weekly "Loyal" DIRAC developers meeting. And, following, the LHCbDIRAC developers meeting.

Zoom: BiLD
https://cern.zoom.us/j/62504856418?pwd=TU1kb01SOFFpSDBJeWVBdU9qemVXQT09

Meeting ID: 62504856418
Passcode: 12345678
 

live minutes
BiLD
Zoom Meeting ID
62504856418
Host
Federico Stagni
Useful links
Join via phone
Zoom URL
Hide
 
 

BiLD – 05/06/2025

At CERN: Federico, Christophe, Alexandre, Theau
On Zoom: Daniela, Simon, Janusz, Robin, Jorge, Ryunosuke, Dhiraj, Xiaomei, Cedric (briefly)
Apologies:

Previous meetings

  • Last BiLD was 3 weeks ago

DIRAC communities roundtable

LHCb:

Federico+Christophe+Christopher+Alexandre+Ryun+Vladimir+Alexey+Robin+Theau

  • NTR

Belle2

Hideki, Ueda, Dhiraj

  • Planning to migrate to OpenSearch for JobParameters.
  • Planning to deploy v9 for certification, issues with extension
  • Dhiraj good progress for RAWBelleDIRAC, which migrated to v9 and using diracx web from k3s. All seems OK
    • performing tests

IHEP

Xiaomei

  • Started using chatbot for DIRAC – using llamaindex
    • setting up a propotype, for the moment just answering questions about DIRAC (documentation)
      • with a DB.
      • One student working on it
    • Alexendre independently, started building a small MCP server for diracx
    • Federico I will bring this one up again at the next meeting, but these initiatives should not diverge

GridPP:

Daniela, Simon, Janusz

  • No change in prod, running v8.0.74.
  • Daniela finally managed to convey her insights (?) from the January hackathon to Simon, so we currently have both of our developement servers using one opensearch instance for testing and having at least nominally RSS enabled.
  • These test also triggered this pull request, which from the GridPP point of view just re-instates previous behaviour:
    • https://github.com/DIRACGrid/DIRAC/pull/8213
    • I know this is not how LHCb does it, but I don’t think 20+ lines of config for a simple on/off switch is appropriate either. #worksforgridpp
      • Federico add the --days switch to the dirac-admin-ban-* scripts and I will accept this
  • We haven’t written it up yet, but we are still hoping to use one IAM server in multi-VO mode, using groups as a stand in for VOs. There were fairly positive noises from Chris^2 that the VOMS2CSSynchronizer could be adapted (can be an option, clearly) to read out the group membership from IAM as well and then match e.g. GridPP IAM + gridpp -> gridpp VO users, GridPP IAM + lz -> lz VO users when generating the user list per VO for DIRACx.
  • from previous meeting When logging into the cvmfs uploader I noticed that we use a lot of space for releases that presumably will never be used: Can we e.g. delete v9.0.0a* up to the release LHCb is using ?
    • ChrisB CVMFS should be de-duplicating things
      • Simon this does not seem the way RAL has set up CVMFS
        Daniela tried to follow up on this last night, but the cvmfs area didn’t seem to be reachable from the uploader. RAL informed.
    • from previous meeting On the other hand, can we please add the latest v8.0 release ? At the moment they stop at 71. (There might be some v8 releases that could go as well.)
      • v8.0.74 now there. But could @Andrei please document the upload procedure in a Wiki or similar, if only to increase the bus factor ?
    • 5th June Federico would you be against moving things to /cvmfs/dirac.cern.ch?
      • go ahead

Topics from GitHub discussions and bots

DIRAC releases

DIRAC projects

DIRAC:

Issues by milestone:

  • v8.0:
    • NTR
  • v9.0:
    • Nothing open
  • After v9.0:
    • Closed 2 today
    • The remaining ones imply DB schema changes.

Other issues:

PRs discussed:

WebApp:

Pilot:

DIRACOS:

  • NTR

Documentation:

  • diracgrid.org being revamped. It will have:
    • info about the consortium
    • generic info, independent from DIRAC and DiracX
    • links to DIRAC and DiracX documentation
  • tasks: https://github.com/DIRACGrid/DIRACx/issues?q=is%3Aissue state%3Aopen label%3Adocumentation
  • Created the DiracX documentation with mkdocs. Hosted on readthedocs.
    • ChrisB registered https://diracx.io/ time ago, linking rtd docs
    • skeleton quite alright, the content needs large revision
      • Christophe there’s a large-ish PR which would require attention but now taken by the restart of LHCb data taking
  • on diracx.io: ChrisB registered it under his name more than a year ago. We do anyway have diracgrid.org (that is also “correctly billed”) so it makes sense to use only that domain. Chris is therefore proposing to move to:
  • non-technical (for publication, presentations): how to write “dirac” – options (the selected ones are in bold):
    • DIRAC or dirac or Dirac
    • DIRACx or diracx or DiracX
    • LHCbDIRACx or LHCbdiracx or LHCbDiracX
    • GridPP: Can’t comment on the last line, but DIRAC and either DIRACx or DiracX. All lowercase always looks like a command not a product.

OAuth2:

  • NTR

management

  • NTR

diraccfg

  • NTR

DB12

Rucio

Tests

  • Robin to improve the (DIRAC-hosted, docker-compose based) integration_tests.py to add DiracX service(s) – basically for testing the legacy adaptors
  • from previous meeting Federico Started adding Rucio to Dirac integration tests
    • –> to Janusz

DiracX:

Issues

PRs discussed:

  • On Pixi : https://pixi.sh/latest/
    • What is pixi? blog post
    • Pixi PR
    • Federico questions:
      • I see a pixi.toml. I thought pyproject.toml was enough
      • should extensions of diracx all use pixi?
      • should I just remove my local diracx and restart?
  • from previous meeting Is fix: #448 and smarter datetimes #454 ready?
    • Jorge looks OK to me but I can’t know all the implications
    • ChrisB It is probably OK, but will try to understand it better
    • Federico bonus question: if it’s ready and can be merged, does it mean that we can give it another go at postgres support?
  • Table summaries
    • maybe use Alembic?
      • it’s a bit weak reason, but why not

DiracX-charts:

  • documentation needs to be fully reorganized (the open PR on it should be included then)

DiracX-web:

  • Theau implemented a way for share app states (dump in JSON, reload through web)

Release planning, tests and certification

  • Certification machines

    • from previous meeting Federico will update it with the latest diracx goodies

  • Next hackathon(s)

    • We should go back at not testing in production (e.g. many changes for pilots from Robin)

  • from previous meeting Few DB changes being prepared (DIRAC):

Next appointments

AOB

LHCbDIRAC

 
There are minutes attached to this event. Show them.
    • 10:00 → 10:10
      Items from Previous BiLD-Dev 10m
    • 10:10 → 10:20
      DIRAC Communities roundtable 10m
    • 10:20 → 10:30
      DIRAC releases 10m
    • 10:30 → 10:55
      DIRAC projects 25m
      • DIRAC
      • WebApp
      • Pilot
      • DIRACOS2
      • VMDIRAC
      • Documentation
      • OAuth2
      • DiracX
      • other externals (include Rucio)
    • 10:55 → 11:00
      Release planning, tests and certification 5m
    • 11:00 → 11:15
      Weekly development(s) focus 15m
    • 11:15 → 11:25
      AOB
      Convener: Federico Stagni (CERN)
    • 11:25 → 11:40
      LHCbDIRAC 15m
Powered by Indico v3.3.7-pre