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) – 20/10/2022
On Zoom: Federico, André, Andrei, Alexey, Alexandre, Christophe, Christopher, Daniela, Hideki, Igor, Simon, Janusz, Vladimir
Apologies:
Follow-up from previous meetings
- hackathon October 13th, on 8.1.0a2:
- Very smooth
- Last BiLD 2 weeks ago
- several “GitHub” discussions answered since then
- agreed to remove Monitoring plotters from v8.0 (only WMSHistory stays)
- defining v8.1 features
DIRAC communities roundtable
GridPP:
Daniela+Simon+Janusz
- v7.3 in production
- Deployed v8.0 on pre-prod server
LHCb:
Federico+Alexandre+Christophe+Christopher+Alexey
- Ran an LHCbDIRAC hackathon on top of v8.0.2
- created [8.0] fix the timestamp of initial logging records, no other issues found
ILC/CLIC/FCC/Calice:
André
- NTR
EGI:
Andrei
- Smooth running, v7.3 py3
- Running special SiteDirector getting a token from TokenManager (actually from oidc-agent – oidc-provider developed)
Belle2
Hideki+Ueda
- Production with v7r2
- Succeded to deploy v7r3 development environment (on py2)
- Created v7.3 py3 pre-release
BES, Juno
Xiaomei
- NTR
NICA
Igor
- Moved production to v7.3.29 py3
- Pilots taking a bit longer (this is normal)
- Developed a simple system to assess the application performance.
Topics from GitHub/Discussions or Google forum
only un-answered topics below:
- Personal certificates with “sn” and “gn” fields not supported?
- Maybe update to VOMS2CSAgent?
- Expose rucio API via DIRAC (DMS/Client/RucioClient.py)
- unanswered. Input expected from Cedric.
DIRAC releases
- v7r3
- v7.3.31
- NTR
- v7.3.31
- v8r0
- v8.0.2
- WorkloadManagementSystem
- CHANGE: (#6399) ElasticJobParametersDB: create a new index every 1M jobs
- CHANGE: (#6381) JobWrapper uses getDestinationSEList rather that resolveSEGroup
- MonitoringSystem
- CHANGE: (#6418) Remove PilotSubmissionPlotter
- CHANGE: (#6386) Remove DataOperationPlotter
- DataManagementSystem
- NEW: (#6381) backport getDestinationSEList from LHCbDIRAC
- Production
- NEW: (#6401) add dirac-prod-complete command
- *Tests
- NEW: (#6381) introduce generateDIRACConfig utility to generate DIRAC config during tests
- Docs
- CHANGE: (#6381) move site documentation from ConfigRef to Resources and dirac.cfg
- NEW: (#6381) document Countries
- WorkloadManagementSystem
- v8.0.2
- v8r1
- v8.1.0a2
- NTR
- v8.1.0a2
DIRAC projects
DIRAC:
Issues by milestone:
- v7r3:
- Still 14 open issues, some will be closed soon (PR open, or nothing to be done)
- v7r3: dirac-admin-kill-pilot fails
- Looking for a better error message
- Add possibility to specify a DIRACOS2 version in SystemAdministrator and Pilot.
- often requested
- AREX CE: the PR should get a final review and be merged
- v8.0:
- 12 open issues, some of them will need to be re-assigned, and/or moved
- v8.0.1 WebApp ssl issue
- PR with fix (draft) created in WebApp, Chistopher care to test?
- Simon I tested and looks OK
- Christopher I would still not be very confident about merging this PR
- Christophe …did not we say in the past that NGINX is becoming mandatory?
- Daniela if we can get away without it, it would be better
- There’s no log about this decision even though it was definitely discussed.
- Christophe
tornadois crap for download, nginx “needed” in this sense
- Andrei do we make nginx mandatory? In this case we should provide proper instructions. Then it should be run on every host (also for https services)
- PR with fix (draft) created in WebApp, Chistopher care to test?
- v8.1:
- 13 open issues, few new ones created
Other issues:
- master branch removal only for readthedocs. It probably makes sense to remove it anyway.
PRs discussed:
- [8.0] Remote Pilot Logger to Tornado. Discussed 3 possibilities for how to pass the options to the pilot scrip:
- from the SiteDirector, with switches (what is implemented right now)
- from the PilotWrapper
- from Pilot/pilotTools.py
- option 2 would be maybe best but it is cumbersome to code it. Option 1 is easiest but leaves out all “vacuum” resources.
- option 2 and 3 both require changes in how the JSON is created.
- [8.0] Pilot stamps available in the pilot execution environment. Janusz confirms that the stamps being passed correctly work for HTCondor and SSH
- should the stamps be added to the web page? for debugging purposes
- [8.0] Tornado log fixes. Christophe: asked Janusz to test it
WebApp:
- NeTR
Pilot:
- Federico Can I merge the PR for
blackfixes?- Christopher you need also py2?
- feat: Enable remote pilot logging using HTTP interface to Tornado
- from previous meeting Q: should we change also the DIRAC logger? in order to use the ISO 8601 format and microseconds. If this is done, then all log messages will have the same format
- an issue should be created with this
- file backend for now, and it will be enough for running the tests. Different backends (e.g. ES) can be added later
- from previous meeting Q: should we change also the DIRAC logger? in order to use the ISO 8601 format and microseconds. If this is done, then all log messages will have the same format
DIRACOS2:
- New version created (https://github.com/DIRACGrid/DIRACOS2/releases/tag/2.26)
- A full singularity installation and a full apptainer installation. Plan to move to apptainer fully, Christopher will start by creating a ApptainerCE (SingularityCE will inherit from ApptainerCE)
- from previous meeting Add htcondor-utils current version (9.11.2), fix diracosrc to use GSI and SCITOKENS auth methods. PR will be added for the latter.
- Christopher if anyone is interested in making a CVMFS-based environment, let me know I will give instructions
Documentation:
- Changed latest to rel-v8r0 (rtd)
OAuth2:
- from previous meeting Any news from issue WLCG and Token transition – reminders and requirements ?
- WLCG timeline document: https://zenodo.org/record/7014668#.YyLag9JBwQ9
- from previous meeting Submitting pilots using tokens, requirements (on Andrei):
- Use at least DIRAC v7.3 py3 server. Will not be available for python2.
- HTCondor client on conda-forge correctly deployed (issue acknowdged by the HTCondor maintainers, but should raised - target version 9.0, not 10.0) – this is needed for M.2 of https://zenodo.org/record/7014668#.YyrDF9JBxD9
- done: 9.11.2 deployed on conda-forge
- oidc-agent deployed on the machine (like an ssh-agent), register one user as a “client”, secret stored locally on the machine
- corollary: puppet should be updated
- bashrc should be adapted
- corollary: puppet should be updated
- SiteDirector needs to be updated for getting token instead of or along with proxy
- SiteDirector needs to be updated to always bundle proxy for getting job
- From 8.0 we can use the TokenManager and then in theory some of the above requirements would drop
tornado/HTTPs
- NTR
management
- from previous meeting 3 issues left, are they still valid?
diraccfg
- from previous meeting Christopher Do we want to make a release that drops support for py2?
- yes
COMDIRAC
- PR created for merging COMDIRAC in rel-v8r0
- Federico thinks that should not be a “simple” merge
- After discussions, agreed on making a bit more polishing before merging
DB12
- Will have to test with py3.10
Rucio
- NTR
Release planning, tests and certification
8.1 release
Proposed features (by Federico, please discuss/approve/dismiss):
- all dips services should have a counterpart on https. An issue with a tick list to follow the progress of services migration to HTTPS should be created
- FileTransfer would have bad performances
- support for non-DIRAC DIRAC client (solving Submitting DIRAC jobs via HTTP and more). A good starting point would be to provide instructions on how to do it for read-only operations, e.g. for monitoring.
- Chris: the general case will not work (there will be limitations). We can get close enough though
- issues: verify them
- deprecate dirac-proxy-init (dirac-login as replacement), then remove it from v8.2
- too early
- remove VMDIRAC (draft pull request: https://github.com/DIRACGrid/DIRAC/pull/6380)
- “done”
Certification machines
- lbcertifdirac70 machine:
- Computing Element of each supported type should be configured (HTCondorCE, 2 ARCS (Alexandre), 2 Clouds (Daniela), SSH). Consider OAuth tests as well - what is needed as far as certification servers configuration is concerned.
- lbcertifdiracoauth machine:
*
Next hackathon(s)
- Next week, on lbcertifidirac70 and with v8.1.a0X
AOB
- ISGC2023 has abstract submission deadline 31/10
- CHEP2023 seems to be happening for real this time. Abstract submission deadline November 17th (very soon!). Leaving it here, proposals welcome.
Next hackathon: October 27th
Next BiLD: November 3rd
LHCbDIRAC
- v10r4: deploy board in https://trello.com/b/kzUKdMts/deploy-v10r3
lbprodupdate: should we move ProxyDB to another instance (separate from the rest)?
- https://lhcb-auth.web.cern.ch/
- We need to have IaM as interface of VOMS (some code need to be developed here)
- For the actual operation we should see (up to Joel).
- LHCbDIRAC hackathon based on 8.0
- At some point (after it will be done on DIRAC certification) we need to setup a CE that accepts token and try out our IAM instance.
- rELEASE on Monday
- ISIMA projects anyone?
There are minutes attached to this event.
Show them.