Choose timezone
Your profile timezone:
BiLD-Dev
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
BiLD
BiLD – 03/10/2023
At CERN: Federico, Vladimir, Alexandre, Andre
On Zoom: Bertrand, Christopher, Cedric, Hideki, Ueda, Janusz, Xiaomei, Alexey, Daniela, Simon, Lorenzo, Andrei
Apologies:
Follow-up from previous meetings
- Last “standard” BiLD on September 14
- Trying to catch all updates below
- Last DIRAC certification hackathon on 21/09 (https://trello.com/b/umOM4dni/v810a20)
- on release v8.1.0a20
- still WMS issues
- BildX on 28/09
- Presentation on DiracX-Web
DIRAC communities roundtable
LHCb:
Federico+Simon+Christophe+Christopher+Alexey
- Running on latest DIRAC v8.0 patch
- First tests using v8.1 pre-release
EGI
Andrei
- v8.0.24 in prod
- Accouting DB growing too large: is it possible to drop the raw records?
- LHCb one is 1.3 TB.
- Federico it’s maybe possible, and maybe it was done already in the past (will check).
- Moving to AREX interface
ILC/Calice/FCC
Andre, Lorenzo
- from previous meeting Regarding VOMS-Admin at CERN (for FCC VO), was told that “VOMS-Admin will most likely not be made available for EL9 and there some VOs that would need to move to the IAM service in the next months (deadline July 2024). Will track progress monthly.”
- Same for LHCb VOMS-Admin? Is DIRAC ready for that?
- It is true for LHCb also, but we do not have a real answer yet.
Belle2
Hideki, Ueda
- Planning to soon deploy v7r3 py3 release
GridPP:
Simon, Janusz, Daniela
- Updated production to 8.0.28. One problem found: https://github.com/DIRACGrid/DIRAC/discussions/7217 (no delegation found on ARC, should be fixed now)
- Alexandre the PR is there, but not sure if it’s making too many delegations. Being tested in LHCb prod on one specific CE.
Topics from GitHub/Discussions
only un-answered topics with discussion updates:
- NTR
DIRAC releases
- v8r0
- v8.0.29
- NTR
- v8.0.29
- v8r1
- v8.1.0a1x
DIRAC projects
DIRAC:
Issues by milestone:
v8.0:
- 15+ open issues
- TransformationCleaningAgent should use the RMS
- implemented in PR 7223, Federico suggests to make this the default.
- Federico probably will “aggressively” close some of them
- TransformationCleaningAgent should use the RMS
v8.1:
- 15+ open issues
- Remove setup from Operations section of CS
- Connected: remove Setup(s) from
Systemsection of the CS. PR https://github.com/DIRACGrid/DIRAC/pull/7186 created but not enough
- Connected: remove Setup(s) from
- from previous meeting Q: would anyone be against in removing ingestion of JobParameters in MySQL table? (reading would stay) (also requested in https://github.com/DIRACGrid/diracx/issues/29)
- This would be a simplification for
DiracX - Would make effectively the use of ES/OpenSearch for JobParameters mandatory
- Connected: https://github.com/DIRACGrid/DIRAC/issues/7191
- will stay until next BiLD
- This would be a simplification for
- Remove setup from Operations section of CS
PRs discussed:
- Mostly reminders about reviewing existing PRs
WebApp:
- NTR
Pilot:
- Federico will:
- align
masterwithdevel(~now) - forbid opening of PRs to
masterbranch - always test
develin DIRAC certification setup (and in github Actions and in Jenkins) - (more) frequently merge
develtomaster
- align
- Federico in order to do the above:
- created an integration test GA workflow, with 3 tests:
- run pilot (but not matching) for different python versions and different DIRAC versions
- run pilot (with matching) for different python versions
- create an LHCb test. The other tests for the different VOs can be added here too.
- partial exposure: not something to pursue now.
- created an integration test GA workflow, with 3 tests:
- Andre Can use a CVMFS action on GitHub actions to mount CVMFS
DIRACOS:
- NTR
Documentation:
- NTR
OAuth2:
- from previous meeting
- Andrei request from EGI to demonstrate that one VO can run with tokens only
- Check In is progressing:
computescopes available, they are accepting the idea of using client access tokens (possibility to associate a client to a given VO). They would probably not accept a same client to deal both with client and user access tokens (security concerns with the scopes available in the clients). - WLCG timeline document: https://zenodo.org/record/7014668#.YyLag9JBwQ9
- Still pending the test for ARC7 and CheckIN tokens
- Multi-VO setup and token tags: Simon F deployed a pre-prod IAM server to Chris^2 using the gridpp VO for testing. (We do not sync with voms server, this is for pilot only).
management
- from previous meeting 3 issues left, still valid?
- Always upload releases to CVMFS is again valid for clients
- higher priority now. This should also be done for non-x86 versions.
diraccfg
- version 1.0 and 1.0.1 created (might be the last…)
DB12
Alexandre
- NTR
Rucio
- NTR
Tests
- N e TR
Release planning, tests and certification
Certification machines
- lbcertifdirac70 machine:
- “should be working”
- from previous meeting Federico not rush, but should we move to a Alma9 box?
- Outside of CERN would be better, in CC probably
- Andrei machine is already there, need to decide how to set this one up
- We could also use the new box to test the installation procedure
- Outside of CERN would be better, in CC probably
Next hackathon(s)
- next week, “standard” v8.1.0aX one.
AOB
Next hackathon: October 12th (Daniela will hopefully be traipsing around Tokyo with Simon in tow.)
Next BiLDX: October 26th
Next BiLD: November 2nd
Workshop approaching.
- Timetable complete, might change a bit. Your input is appreciated, and there’s a document (https://cernbox.cern.ch/s/DNZcRP5KCsbvVZ7) for sharing discussions, mostly for the hackathon session.
Daniela if we need openssl in every WN, this should come from HepOS list requirements
LHCbDIRAC
- v11.0: deploy board in https://trello.com/b/Ep0PAkbv/deploy-110
- NTR
- Nex hackathon on 25th (just after the workshop)
- Federico will create the release before
There are minutes attached to this event.
Show them.