BiLD-Dev
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) – 28/01/2021
At CERN: Still, nobody :/
On Zoom: Federico, Alexandre, André, Andrei, Andrii, Christophe, Christopher, Daniela, Hideki, Igor, Janusz, Marko, Simon, Xiaomei, Ueda
Apologies:
Follow-up from previous meeting
-
Ran hackathon last week on v7r2-pre31:
- trello board here
- Some quite minor issues discovered, but in general it looks quite OK
- https functionalities not yet tried out
-
PR [v7r2] Fully support setuptools merged – last large PR for v7r2
DIRAC communities roundtable
GridPP:
Daniela
- Tested v7r1p26 and looks fine, going into production with it today.
CLIC:
André
- NTR
LHCb:
Federico
- Moved to v7r1 last Monday
- In general, quite smooth transition
- In v7r1, the StalledJobAgent checks only jobs in Running and Completing status, and no longer in Completed status, but we have a bunch of old v7r0 jobs that finished in such a status after the release was deployed. ==> Set these jobs “Failed”
- BDII2CSAgent now looking in Glue2 added in CS several 8-core queues from ARC CEs. PR https://github.com/DIRACGrid/DIRAC/pull/4926 adds also “Pool” as LocalCEType for them (also at the queue level). Needs also https://github.com/DIRACGrid/Pilot/pull/125
- A few things still to activate, e.g. JobParameters on ES, Singularity Inner CE, a few others
EGI:
Andrei
- Preparing the migration. Resources almost all in place.
- Updating to v7r1 while doing the migration.
France Grilles:
Andrei
- Still on Pilot 2.
- Added PR (for v7r1) for accessing ES via certificates: https://github.com/DIRACGrid/DIRAC/pull/4924
Belle2:
Hideki+Cedric
-
WebApp: haven’t investigated in details
- Hideki I hope that the change to tab view would not happen together with v7r0
- Federico no, that would happen only in v7r2.
- In the meantime can migrate to Tab view yourself.
- Hideki I hope that the change to tab view would not happen together with v7r0
-
rucio migration:
- [slides on the agenda]
- migration successful, now running normally
- code:
- DIRAC-RucioCatalog implementation as per PR – had to slightly amend it
- added 2 agents for sync of DIRAC users and SEs info to Rucio
- No big issues during the final transition, but some: highlighted in the slides
- Ueda Maybe the RucioCatalog can’t be shared because of user mapping, especially not sure for multi-VO setup
- Andrei if Rucio accepts X509 certificates, why not user the DN?
- Ueda in Rucio you can have more than 1 account per DN (but also the contrary). The logic is in general different.
- Janusz we are pretty far from a stable system, even the multi-VO rucio server is not there yet.
JINR
Igor
- Security has not turned on FC yet, will first update DIRAC version
- VMDIRAC using Pilot2 (but using quite old v7r0pxx version)
- watchdog disable “proper trick” does not work there. So for the moment we found a workaround.
- Need to update to latest version of DIRAC v7r0
- Simon should be possible to use Pilot3 with latest versions on VMDIRAC.
Juno, BES3:
Xiaomei
- NTR
DIRAC releases
- v7r0p45 + 46:
- (#4899) JobAgent: adding ExtraOptions as argument iff the executable is a DIRAC script
- (#4896) ARC CE: request all processors on the same node.
- *v7r1p26:
- Minor fixes
- v7r2-pre31:
- DIRAC scripts now with
_instead of- - Some python3 compatibilities fixed
- Now creating also tags for pip
- DIRAC scripts now with
DIRAC projects
DIRAC:
PRs
- [v7r1][WIP] docs: user manage, proxy manager for addressing https://github.com/DIRACGrid/DIRAC/issues/4702
- some of the documentation requested is not for v7r1, rather for v7r3
- What’s prepared should be close to final anyway
- Christophe should look again into it (one final time)
Issues
- v7r0:
- 2 issues right now
- dirac-proxy-init silent fallback to /etc/vomses Marko will take care ASAP
- v7r1:
- Still some tasks in there, some are for documentation
- all the others are not urgent
- v7r2:
- see below
- v7r3:
- Not discussed
WebApp:
PRs
- PR documentation on nginx configuration was removed, created a new one
Issues
- from hackathon: ComponentMonitoring issue, will need to look into it.
- once he has an CERN account…
Pilot3:
PRs
- https://github.com/DIRACGrid/Pilot/pull/124 added a Pilot-python3 test (merged)
- https://github.com/DIRACGrid/Pilot/pull/125 gets LocalCEType from queue section, if it’s there
- can it be merged?
Issues
- https://github.com/DIRACGrid/Pilot/issues/120 (Pilot3 adds “pilot.cfg” on to user argument list)
- fixed
DIRACOS:
- new gfal version – pain with SLC6 deprecation
- these pains will be more and more
- struggles to keep python2 in:
- We should, in general, move as fast as possible to DIRACOS2
DIRACOS2:
- the only thing that we consider missing as of now: fts-rest python3 (still waiting, not depending from us).
- When installing python 3, we are still installing from Chris B fork
Reminders:
- DIRACOS2 is for python3 only. No efforts will be ever put into python2.
- It will be offered for client installations only starting from DIRAC v7r2
- for v7r3 we maybe make it as default for client installations
- Future versions should flip the flag of the client, and offer a server python3 installations (which right now is broken, won’t look for fixing it in v7r2)
VMDIRAC:
- NTR
Documentation:
- Missing doc for [v7r1] Update the documentation for the new organisation of FC components Andrei
OAuth2:
- WIP
tornado/HTTPs
- It’s time to start testing it: Christophe will add a task in Trello board. Will enable DFC as https service (waiting for access).
management
- Task https://github.com/DIRACGrid/management/issues/10 Andrei + Marko is being addressed.
diraccfg
- NTR
other externals, including Rucio
- N else TR
Release planning, tests and certification
-
Certification machine updated to be multi-VO (task: https://github.com/DIRACGrid/DIRAC/issues/4631)
- Daniela Can we have another go at adding it to certification setup?
- Federico Sure, I will modify the trello task for that and we can start with the next hackathon
- Daniela Can we have another go at adding it to certification setup?
-
Next hackathon
- next week (4th Feb), already called.
Weekly development(s) focus
What’s left for DIRAC v7r2 “final” tag?
Out of what is in https://github.com/DIRACGrid/DIRAC/milestone/20:
- Update dirac-install for DIRACOS2 Christopher
- Move integration tests under /tests Christopher
- Convert old Monitoring into new style in ExecutorDispatcher Christophe
- Some part of Move dirac-install to management repo Christopher
needs:
- current PRs merged, before Christopher goes ahead with last PRs
- fts-rest in DIRACOS2
Others?
- Make RSS vo-aware Janusz: working on it right now, will make a draft PR.
AOB and topics from Google forum
NTR
Next hackathon on February 4th: https://indico.cern.ch/event/1001395/
Next BiLD on February 11th: https://indico.cern.ch/event/1001396/
LHCbDIRAC
-
v10r2 planning in https://gitlab.cern.ch/lhcb-dirac/LHCbDIRAC/-/wikis/Releases-planning#based-on-dirac-v7r2
- we want anyway, before restarting to do hackathons to first update the certification setup with what we put in https://codimd.web.cern.ch/2es8HPUcSmS42jrTxhX3JQ?both
- which actually should be expanded by Chris and Chris
- we want anyway, before restarting to do hackathons to first update the certification setup with what we put in https://codimd.web.cern.ch/2es8HPUcSmS42jrTxhX3JQ?both
-
proposal for new ProductionManagement
- discussed by Chris+Federico at the end of the meeting
- main summary: concepts will stay the same, adding a new layer on top to simplify the life of Mihail+Gloria+etc.