BiLD – 27/11/2025

At CERN: Federico, Christophe, Christopher, Ryun, Alexandre
On Zoom: Ueda, Daniela, Hideki, Alexei, Natthan, Mazen, Jorge, Xiaomei, Vladimir
Apologies: Andrei

Previous meetings

• Last BiLD was 2 weeks ago, and 1 week ago we had a certification hackathon

DIRAC communities roundtable

LHCb:

 Federico+Christopher+Christophe+Alexandre+Ryun

• NTR

Belle2

 Hideki, Ueda

• OpenSearch discussion: how long to keep data. Suggestion is to open a discussion for sharing best practices.
• from previous meeting Scalability issues: MySQL. Probably caused by many short jobs
• from previous meeting Found some stomp related issues, will check if already signaled, if not will create a new one

Juno+BES3:

 Xiaomei

• Wants to clean VOMS- discussion to be open
• from previous meeting Forced to use Multi-hop. Mostly successfull, but issues reported
  •  Chistophe saw the issues, will look at it soon
  • a PR has been created, to be tried.

EGI

 Mazen

• from previous meeting Created GreenDIRAC extension for keeping related developments: GreenReportingAgent, energy consumption by jobs tool (Mazen)
  • Submitting energy metrics for each job into the DB
• from previous meeting Started a GreenSiteDirector
  • work in progress, for submitting to sites that have a lower energy footprint
• from previous meeting Got functional D9/Dx0.0.1 certification installation (Bertrand):
  • DIRAC9 host + 2 hosts k3s cluster for DiracX + S3/minIO
    •  Chris+Federico should not run on 2. Better 1 or 3
  • Opensearch with certificate authentication
    • will contribute to DiracX for this
  • IAM dev IdP, failed with dteam IAM, Check-In in progress
  • wants to add also a MQ

GridPP:

 Daniela, Simon

• Nothing to report for production, all other issues we have are logged on git.

CTAO:

 Natthan

• Nothing to report for production
• New version of Helm charts deploying DIRAC, DiracX, IAM, Rucio, in Kind.

Topics from GitHub discussions and bots

• DIRAC and DiracX topics with discussion updates:
  • FTS3 job status updating failed when using multi-hop transfer #8337
    • Maybe solved by https://github.com/DIRACGrid/DIRAC/pull/8386
  • Renewal of payload proxies #8369
    • any idea?

Releases

DIRAC

• v8.0.77
  • NEW: (#8256) Included a VO (using top level groups as VO) option when getting user subjects from IAM. Behaviour with single VO IAM should be unchanged.
• v9.0.8
  • NEW: (#8263) add scitag to FTS transfers
    • Can be used by whoever configured scitag – e.g. Belle2
• v9.0.9
  • CHANGE: (#8359) Subprocess: use psutil for killing processes
• v9.0.10
  • Few fixes following the last hackathon
  • CHANGE: (#8373) This contains various speed of for the TS, mostly by using temporary tables for the queries, only requesting what’s needed in the DB, and bulking things more efficiently

Issues (still there?):

• from previous meeting https://github.com/conda-forge/dirac-grid-feedstock/issues/170 https://github.com/conda-forge/dirac-grid-feedstock/issues/169
  •  cburr will take care of these ASAP

DiracX

• v0.0.2
  • created weeks ago
•  Federico I will start merging in a few PRs by next week (things that will need to go through a hackathon). Maybe create 0.0.3 now?

Release planning, tests and certification

• Upgrade to v9+0.0.1:

  • No news

• Certification machines

  •  Federico added 1 person from CMS (in dteam VO) – submitting few jobs
  •  Federico added the diracx_admin VO. Somehow not working fully …?

• Next hackathon(s)

  • in 2 weeks, with actually code that needs careful testing

DIRAC projects

DIRAC:

Issues by milestone:

• v8.0:
  • from previous meeting
    • Add config option to prevent some groups from cleaning transformations
      •  Federico assigned to me, can I assign to someone from Juno?
    • Don’t block the transformation system if owner is removed
      • Xiaomei to give more details
    • RucioFileCatalogClient.setMetadata returns empty result on success
• v9.0:
  • A commit in the CS should verify the diracx verification #8302 solved in https://github.com/DIRACGrid/DIRAC/pull/8351 – review OK?
• v9.1:
  • NTR

Other issues:

• Get infos from CRIC
  • any volunteer?
• Replacement for BDII2CSAgent #8194
  • 13th Nov New updates in https://helpdesk.ggus.eu/#ticket/zoom/3427
    •  Andrè (enthusiastically?) volunteered ;-)
    • GOCDB has agreed to implement the scopes as we originally asked for.
    • As a test, we implented scopes for ilc and t2k.org, that the sites can set for their services.
    • Once Andre S has finished his DIRAC side tests, we can submit a GGUS ticket and they will generated scopes for all the VOs we give them.
    • Then we just need to find a way to diplomatically phrase an EGI broadcast, so we hopefully don’t have to contact all sites individually.

PRs discussed:

• from previous meeting [9.0] feat: SSHCE export inputs/import outputs as a JSON file to handle more jobs in parallel #8362
  • draft but hotfixed in LHCb
• from previous meeting [9.0] Avoid endless loop in MonitoringReporter #8363
  • just a question to answer in there
• from previous meeting feat: verify CS config commit using diracx model validation #8351
  • This is ready (?)
• from previous meeting [9.0] Use DIRACX_CA_PATH to communicate to diracx and S3 #8364
• 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

WebApp:

• NTR

Pilot:

• PR for removing Python2 support re-created (previous one introduced a bug)
  • Tested in hackathon, will be merged into master when all tests pass (pending RAL support @@)
  • from previous meeting if you really want to keep py2 support, there’a tag

DIRACOS:

• PR linked to https://github.com/DIRACGrid/DIRAC/pull/8382

Documentation:

• from previous meeting tasks: https://github.com/search?q=org%3ADIRACGrid is%3Aissue state%3Aopen label%3Adocumentation &type=issues
  • including some for diracx-charts and diracx-web
• from previous meeting  Andrei Need documentation on how releases are made

management

• Having again issues for /cvmfs/dirac.egi.eu (the syncing was not happening, ticketed, etc.). No monitoring on their side, urgent need to move out.
• from previous meeting new /cvmfs/dirac.cern.ch repository created – CERN ticket
  • action on  cburr to populate it (using LHCb “machinery”)

DB12

• NTR
• from previous meeting  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
• from previous meeting We should agree on a strategy on how to do things here, as PRs can’t just be merged:
  • there are reports created that depend from it, merging/releasing on a random Tuesday is not the way to go
  • can we have parallel benchmarks? not clear actually if that’s doable
  •  Federico maybe create a “2026” release?
    • we should see if there would be time for that

Rucio

• from previous meeting CTAO submitted draft PR https://github.com/DIRACGrid/DIRAC/pull/8327 and issue https://github.com/DIRACGrid/dirac/issues/8331
  • 23 Oct 25  Federico I asked Cedric to review these and other Rucio issues/PRs, but “no time”.

Tests

• NTR

DiracX:

• dependabot alert for web
  • NTR

Issues and Discussions

• Support of ISB in jobs submit CLI
  • but the main question here is where to code “submit_job (with a ISB)”
  • developed into PR InputSB support #711
    • some issues in there, e.g. the “assignement” should be done eventually by the tasks
• CS repo directory problems in container deployment #700
  • How to use LocalGitConfigSource?
  • needs follow-up
• Problems running a “development” diracx container #704
  • needs follow-up

PRs discussed:

• All PRs have failing tests:

Error: plugin source does not support verification. Use --verify=false to skip verification
Cleaning up

• fix: Remove LocalGitConfigSource and replace with FileGitConfigSource
• feat (Configuration): add documentation to CS attributes; sub_from_preferred_username uses cache #696
  • • 2 other PRs for generating documentation. 2 of them ready for merge.
• from previous meeting Alembic and triggers
  • asked  Cedric to review it
• from previous meeting feat: deploy gubbins images #527
  •  Federico I rebased it but still failing

CWL prototype

• “moving” with full plan in https://codimd.web.cern.ch/tUL0IUMKT56tsNv3dAf65w?view.
  • will give a report at next BiLD

DiracX-charts:

• from previous meeting Moved to fixed versions in diracx/values.yaml and added automatic chart version bumping on DiracX releases
  • Similarly should be done for diracx-web

DiracX-web:

• NTR, but many “bumps” PRs

Next appointments

• Meetings:

  • DIRAC(X) cert hackathon in 2 weeks
  • BiLD: in 3 weeks (last of the year)

• WS/hackathons/conferences:

  • DiracX hackathon 21st-22nd January 2026: https://indico.cern.ch/event/1582395/

AOB

• It’s again CHEP abstract submission time, deadline 19th December

  •  Federico wrote a short one: https://codimd.web.cern.ch/ErBx4tqjSV-VC5zHMq1OXw
    • will submit this by the next BiLD meeting, in the meantime please comment

• ISIMA:

  •  Federico+ChrisB+Alexandre wrote down a proposal for a new Jobs Matching mechanism for DiracX: https://codimd.web.cern.ch/eOU4kV3jRTSSJq43FXvhwg#, https://codimd.web.cern.ch/bCva5aa3SpWELiox3_yq9w#
    • idea would be that student prepares a prototype for stress tests (e.g. 10M jobs in queue, how fast can we match?)
    • (new) description of job requirements to be used will need your suggestion

• from previous meeting DIRAC as an “HSF affiliated project” : https://hepsoftwarefoundation.org/projects/affiliated.html

  • 13th Nov 2025 no news, but in the meantime this was presented at few forums (…). In the meantime Ruslan restarted the evaluation.

LHCbDIRAC

• The Pilots respect the PreferredURL regex – see improvements?
• CHEP abstracts in https://codimd.web.cern.ch/4mOg3RgsT1eVTnb4KT3Tuw?edit
• ISIMA interview?
• from previous meeting The CS in lhcbdiracx has not been updated lately because of new fields added which do not pass the validation
  • so no new users in the last 10 days
  • protection from that is in the works (issue in DIRAC attached to Natthan)
• Several MRs in the system, reminders to update the existing ones and check what’s actually ready for merge
• Bookkeeping
  • We should change the passwords of our dirac users - new should be at least 15 characters long – maybe no need (?)
  • Repartition done – are we happy?
    • Yes!
  •  
  • PRs:
    • add materialized view for processing paths optimization
      • this should be merged first and the next ones use it
      •  Alexey it does not work for me, see comment in MR
    • reworked addProcessing
    • reworked getproductionporcpassname
• mc submit:  Alexandre starting development for fully getting out of “templates”
• PoolCE should be interpreting a signal for stopping to process jobs.