Choose timezone
Your profile timezone:
BiLD-Dev
→
Europe/Zurich
Description
Bi-Weekly "Loyal" DIRAC developers meeting. And, following, the LHCbDIRAC developers meeting.
Join Zoom Meeting
https://cern.zoom.us/j/91083694183?pwd=ZkdDY1I1YkJVc2o3UTdBY1BRZE15UT09
Meeting ID: 910 8369 4183
Passcode: 12345678
One tap mobile
+41432107108,,91083694183# Switzerland
+41315280988,,91083694183# Switzerland
Dial by your location
+41 43 210 71 08 Switzerland
+41 31 528 09 88 Switzerland
+41 43 210 70 42 Switzerland
+33 1 8699 5831 France
+33 1 7037 2246 France
+33 1 7037 9729 France
Meeting ID: 910 8369 4183
Find your local number: https://cern.zoom.us/u/artUfAdNB
Join by SIP
91083694183@188.184.89.188
91083694183@188.185.118.153
Join by H.323
188.184.89.188
188.185.118.153
Meeting ID: 910 8369 4183
Passcode: 12345678
BiLD (Bi-weekly DIRAC Development meeting) – 23/03/2023
On Zoom: Federico, Andrei, André, Alexey, Alexandre, Bertrand, Cedric, Christopher, Daniela, Lorenzo, Janusz, Simon, Ueda, Hideki, Xiaomei, Vladimir
Apologies:
Follow-up from previous meetings
- Last BiLD 2 weeks ago
- all updates below
- Hackathon last week on 8.1.0a11 – https://github.com/DIRACGrid/DIRAC/releases/tag/v8.1.0a11
- Ran with https://github.com/DIRACGrid/DIRAC/pull/6653 patched in, few issues fixed
- Started late, with fewer than usual participants, and did not run every test
DIRAC communities roundtable
LHCb:
Federico+Alexandre+Christophe+Christopher
- NTR
EGI
Andrei
- Moved most of the service to 8.0.17. Few services not moved, but will be done this week.
- Bertrand Exploring FluentD for Tornado services logs
- End schema in ES should be the same as the Logstash setup
- Already able to see logs in Kibana, looking also for Grafana
- Will explore also FluentBit (?)
ILC/CLIC/FCC/Calice:
André, Lorenzo
- NTR
Belle2
Hideki, Cedric, Ueda
- Finishing validation of v7r3. Need new release of v7r3.
- Trying grafana. Version 9 is OK?
- Federico I guess so, but I am unsure
GridPP:
Daniela, Simon, Janusz
- No changes in Production, is there any chance of another v7r3 release, please ? (On a related note: Would it be possible to remove some of the old tags (especially the pre-releases once we have a proper one), I get carpal tunnel syndrome from scrolling.)
Juno/BES3:
Xiaomei
- NTR
Topics from GitHub/Discussions or Google forum
only un-answered topics with discussion updates:
DIRAC releases
- v7r3
- NTR, but a new release should be created
- v8r0
- Last one is v8.0.18
- Only fixes, nothing important to report
- Last one is v8.0.18
- v8r1
- Mostly fixes from the hackathon
DIRAC projects
DIRAC:
Issues by milestone:
v7r3:
- 2 open issues – 1 now
v8.0:
- 26 open issues, several to re-evaluate + re-assign --> mostly for Andrei and Alexandre
- Requirements and tasks for token-based pilot submissions
- Maybe can be closed?
- Tokens: ssid should not be added as a DN
- no updates
- Mix of groups for ReportGeneratorHandler
- Seems somewhat urgent, but no updates since last time. Very difficult to reproduce it
- Requirements and tasks for token-based pilot submissions
v8.1:
- 21 open issues
- (for PilotLogging) find the VO from the proxy (and from the token)
- re-assigned to Federico for dealing with the “HLT” pilots
- Related, for v8.0 already: PilotLogger - How to identify pilots in an early submission state
- (for PilotLogging) find the VO from the proxy (and from the token)
Federico In general, issues list by milestone is too long. Some issues will be moved to v8.2 milestone (to be done)
- gLogger and external libraries: discrepancies
- openssl 3.1.0 breaks lhcb-proxy-init
- Opened an issue against openssl: https://github.com/openssl/openssl/issues/20555, already a PR open with a fix
PRs discussed:
- [TBD][v7r3] test (CI): use github registry instead of docker
- anything for management repo?
WebApp:
- Refurbished TokenManager WebApp
- need to be added in some puppet profile?
Pilot:
DIRACOS2:
- Python 3.11 seems to be fine
- Propose to update immediately after OpenSSL 3
- from previous meeting Opened an annoucement about OpenSSL 3
- Included a script to allow others to check if they have affected sites
- Please try it and report the results (and ticket sites if needed)
- Included a script to allow others to check if they have affected sites
- from previous meeting OpenSSL 3 (originally reported by Rucio): important performance degradation: https://github.com/DIRACGrid/DIRAC/discussions/6851#discussioncomment-5190607 also observed by DIRAC, ticket opened in https://its.cern.ch/jira/browse/DMC-1372
- OpenSSL 3.1 mostly sorts out the issue above
Documentation:
- NTR
OAuth2:
- from previous meeting
- WLCG timeline document: https://zenodo.org/record/7014668#.YyLag9JBwQ9
- Meeting note from 8/12/2022: https://demo.hedgedoc.org/cWl2Y5MtTwSn4V5Uic_K5w
- Issue Expand integration tests for IaM
- PR https://github.com/DIRACGrid/DIRAC/pull/6882 there to sort out this issue, but several discussions trasfered to issue DIRAC Configuration structure to interact with Identity Providers
- Alexandre the PR is ready to be reviewed
- Andrei will review
- PR https://github.com/DIRACGrid/DIRAC/pull/6882 there to sort out this issue, but several discussions trasfered to issue DIRAC Configuration structure to interact with Identity Providers
tornado/HTTPs
- from previous meeting Issue https://github.com/DIRACGrid/DIRAC/issues/6495 keeps track of what can and what will not be moved to https
- no updates for today
- from previous meeting Federico we need to try and propose a coherent update from DIPS to HTTPS services, e.g. for Configuration Services URLs
management
- from previous meeting 3 issues left, still valid
- NTR
diraccfg
- version 1.0? still tbd
COMDIRAC
Daniela
- As we so far had no input, we are going to take this as a “yes” and go ahead with our nefarious plans to improve the code.
DB12
Alexandre
- NTR
Rucio
- NTR
Tests
- Moving to HTTPs services as defaults in PR
- Temporarly disabled MultiVoFileCatalog service
- how to make it “equivalent”? some comments in the PR
- Temporarly disabled MultiVoFileCatalog service
Release planning, tests and certification
Certification machines
- lbcertifdirac70 machine:
- NTR
- lbcertifdiracoauth machine:
- Do we still need this machine? Now it seems we are at the level that only lbcertifdirac70 is needed.
- prob not, can be destroyed
- Do we still need this machine? Now it seems we are at the level that only lbcertifdirac70 is needed.
- Federico not rush, but should we move to a Alma9 box?
- Outside of CERN would be better, in CC probably
- We could also use the new box to test the installation procedure (now we have mostly HTTPs services)
- ?? Alternatively, or together with it, it would be nice to have a K8 setup
Next hackathon(s)
- March 30th on lbcertifdirac70
AOB
Next hackathon: March 30th
Next BiLD: April 13th
(still private): DIRAC+Rucio WS https://indico.cern.ch/event/1252369/. You can anyway start booking your flights.
LHCbDIRAC
- v11.0: deploy board in https://trello.com/b/Ep0PAkbv/deploy-110
- Singularity CE everywhere?
- https://security-issues.web.cern.ch/incidents/155564
- https://lhcb-auth.web.cern.ch/
- from previous meeting Alexandre An admin can allow a user (a client actually) to get access to the
compute.cancel/create/modifyscopes. Chris allowed Andrei and I to get access to the compute scopes, thus we should be able to use our clients to submit pilots. - Alexandre Created an Client for the ETF tests
- from previous meeting Alexandre An admin can allow a user (a client actually) to get access to the
- Federico I suggest to have a LHCbDIRAC hackathon with the only real goal to verify the token pilot submission. This would verify that:
- what’s in the code is correct not only for wlcg
- the instructions are correct
- LHCb IaM instance is correctly configured
- LHCb has few resources that accept tokens
- In CC we should have one
There are minutes attached to this event.
Show them.