BiLD-Dev

Name: BiLD-Dev
Start: 2025-10-09T10:00:00+02:00
End: 2025-10-09T12:00:00+02:00
Location: CERN

Thursday 9 Oct 2025, 10:00 → 12:00 Europe/Zurich

2/R-014 (CERN)

2/R-014

CERN

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

62504856418

Federico Stagni

Join via phone

Hide

BiLD – 09/10/2025

At CERN: Federico, Christophe, Christopher, Ryun
On Zoom: Dhiraj, Daniela, Simon, Janusz, Hideki, Alexei, Natthan
Apologies: Andrei

Previous meetings

Last BiLD was few weeks ago, before the DUW.
At DUW (https://indico.cern.ch/e/duw11):
- 15 to 20 active participants. Notable absent: CTAO
- active hackathon sessions, with work done. Not too much hacking, mostly solving (trying, at least) specific installation issues.
- several issues wrote down, and other follow-ups

DIRAC communities roundtable

LHCb:

Federico+Christophe+Christopher+Vladimir

We are seeing issues with CS becoming unavailable. Trying to understand why. Several attempts to fix it have been done, maybe now after PR https://github.com/DIRACGrid/DIRAC/pull/8323 and increasing the number of threads for all CS to 50 we are better.

Belle2

Hideki, Dhiraj

BelleRAWDIRAC built with DIRAC v9. Only installing DiracX with only AuthDB

CTA:

Natthan

NTR
Thanks for the quick fixing in DIRAC!

GridPP:

Daniela, Simon, Janusz

No news from production.
Looking at v9 upgrade, currently several iterations deep into database updates. Please check the certification mattermost if you are interested in the gory details.

Topics from GitHub discussions and bots

only un-answered DIRAC and DiracX topics with discussion updates:
- NTR

Releases

DIRAC

v8.0.76
- Resources
  - CHANGE: (#8214) SLURM plugin now supports the WholeNode options
- ResourceStatusSystem
  - CHANGE: (#8213) Added a token expiry option to dirac-rss-set-status and dirac-admin-allow/ban-site commands.
v9.0.0
- Tagged during the workshop
v9.0.1
- WorkloadManagementSystem
  - FIX: (#8321) Restore uploading local outputfiles from the job’s directory to a specific LFN.
- RequestManagementSystem
  - CHANGE: (#8303) REA defaults changed for higher perfs

diracx

Last one is v0.0.1a50

Release planning, tests and certification

Federico During the workshop DIRAC v9.0 have been tagged, but:
- nothing else (e.g. WebAppDIRAC, diracx*)
- for DIRAC there’s still only integration branch (~same for WebApp)
  - we’ll keep using the integration branch for now
- shall we proceed with the rest?
  - Chris+Chris we’ll implement the feature about partitioning of the DB, tbd tomorrow, and then we can do all the tagging
Upgrade to v9+0.0.1
- the wiki has been updated and is by now the official source of documentation for the update
  - do not look anymore in the codiMD note
  - it makes several references to
    - the official doc (diracx.diracgrid.org)
    - gist scripts maintained by Federico
      - have been updated after bug reports by Daniela
      - feel the need for being given editing rights?
        
        maybe move to “management” repo?
Certification machines
- Federico not updated (no time)
Next hackathon(s)
- Federico will call one once the cert machines are updated – probably in 3 weeks from now

DIRAC projects

DIRAC:

Issues by milestone:

v8.0:
- Add config option to prevent some groups from cleaning transformations
  - Federico assigned to me, can I assign to someone from Juno?
- CS Slave refreshing from itselfs
  - Questions for Juno to be answered
- Don’t block the transformation system if owner is removed
  - Xiaomei to give more details
- RucioFileCatalogClient.setMetadata returns empty result on success
v9.0:
- Job Pre/Post processing flexibility
  - needs Alexandre
- A commit in the CS should verify the diracx verification
  - Natthan volunteered
v9.1:
- NTR

Other issues:

Proposal for input data resolution format
- also cited in https://github.com/aldbr/dirac-cwl-proto/issues/25
- question for all:
  - Is the “PoolXML” a LHCb-only utility? anyone else using it?
- the XML “catalog” is created within the DIRAC (and LHCbDIRAC) InputDataResolution Workflow module. It is then looked it up (!) in the JobWrapper, creating a warning message if it is not there.
Get infos from CRIC
- any volunteer?
Make the PushJobAgent compatible with more CEs (HTCondor? SSH?)
- Federico Who is requesting it?
Not blocking REA because of slow removal at a site
- any volunteer? --> Christophe
Make pixi task docs generation run in CI
- Federico pixi? this is DIRAC doc --> moved to diracx
from previous meeting Replacement for BDII2CSAgent #8194
- “nice” discussion
- 17th July
  - recent answers in the GGUS ticket above from AP seems to point in the right direction
  - nevertheless, Federico is trying to grab info on if we can do a “CEs” crawler ourselves. ARC CEs seem to provide the necessary information, issues are from HTCondorCEs
- This has now been discussed in the GridPP project management board. Conclusion was unfortunately “input from GOCDB team needed”
- 09 Oct 2025 GridPP ops team asked UK sites to implement Alessandro’s suggestion. The following issues were observed:
  - It’s not documented (beyond a soon tobe archived broadcast)
  - Free form encourages typos and misremembered VO names (vo.na62.gridpp.ac.uk vs na62.vo.gridpp.ac.uk) – this would not happen with predefined scopes
  - RAL as the Tier 1 hit the length limit for extension as it supports too many VOs
  - Sigh.
    - Last message from Federico:
    For those of you who are running a HTCondor CE, would you mind investigating if the content of auth-map + accounting-map files could be made public? Maybe we are lucky and it’s a trivial thing to be done.
    - Daniela This has gone to the HTCondor developers via RAL, but so far no answer.

PRs discussed:

The PRs:
- [8.0] IdP clients per user group
- V9.0 feat fts direct tokens
- requires some coordination – Christophe to sort these ones out
from previous meeting add scitag support
- “re-written” and ready to merge
from previous meeting PoolCE and RAM (issue raised in https://github.com/DIRACGrid/DIRAC/issues/7853#issuecomment-2948565279): https://github.com/DIRACGrid/DIRAC/pull/8232
- no progress lately

WebApp:

Pilot:

As agreed at the workshop, there’s a PR for removing Python2 support
- review please! – or will be merged by the next BiLD
- if you really want to keep py2 support, there’a tag
from previous meeting Pilot migration
- diracx pilot route
from previous meeting PR feat: Adding JWT support alongside X509 auth
- the new Pilot command can call directly the route, no need to use the CLI
- the integration tests for this will be set up once diracx is updated with the connected diracx PR

DIRACOS:

Documentation:

diracgrid.org
- source is at https://github.com/DIRACGrid/diracgrid.org. Effectively hosted on github pages
  - Federico is this visible in China?
- DNS adjusted for DIRAC and diracx docs (which are hosted at readthedocs) and chart
from previous meeting tasks: https://github.com/DIRACGrid/DIRACx/issues?q=is%3Aissue state%3Aopen label%3Adocumentation

management

from previous meeting new /cvmfs/dirac.cern.ch repository created – CERN ticket
- action on @cburr to populate it (using LHCb “machinery”)

DB12

Federico “I asked Igor if he wanted to become one if not the main maintainer”
- revived https://github.com/DIRACGrid/DB12/issues/9
- create https://github.com/DIRACGrid/DB12/issues/15 and made a suggestion that can be accepted
- PR https://github.com/DIRACGrid/DB12/pull/16 created – will wait for Alexandre for review

Rucio

CTAO submitted draft PR https://github.com/DIRACGrid/DIRAC/pull/8327 and issue https://github.com/DIRACGrid/dirac/issues/8331

Tests

DiracX:

dependabot alert for web
- N interesting TR

Issues

Nothing specifically discussed