BiLD (Bi-weekly DIRAC Development meeting) – 22/04/2021
At CERN: Still, nobody :/
On Zoom: Federico, Alexandre, André, Andrei, Andrii, Christophe, Christopher, Daniela, Hideki, Igor, Janusz, Marko, Simon, Xiaomei
Apologies:
Follow-up from previous meeting
DIRAC communities roundtable
GridPP:
Daniela
- Nothing to report wrt the production instance.
- We have advertised the DIRAC workshop to our users, but they are unlikely to engage directly with DIRAC.
- On Monday we saw an overload of the file catalog, which is rare, but we were wondering what ‘typical’ access rate for e.g. LHCb is ?
CLIC:
André
LHCb:
Federico+Chris+Chris+Marko
- Nothing interesting to report
EGI + France Grilles:
Andrei
Belle2
Hideki
- v7r0 migration ongoing.
- Trying to use webdav protocol
- some sites are crushing.
libcrypt issue
- the suggestion is to try with DIRACOS v1r18
- Andrei I got rumors that you are thinking to submit DIRAC pilots to Panda for accessing HPC sites.
JINR
Igor
- Also seen proxies renewal issues (looks very similar to EGI issues)
- Tried to use TransformationSystem for MC
- looks promising.
- next step is to start running jobs according to input data
- Looking into DB12. Some tests will be shared.
BES3+JUNO
Xiaomei
- Doing upgrade. Also trying webdav
- How to remove replicas?
DIRAC releases
- v7r1p38:
- *v7r2p4:
- New integration tests. As PR 5094 has been merged, it means that you should update your integration tests accordingly, in case you were using them in your extenion. E.g. LHCb GitLab-CI tests
- v7r3-pre5:
- Just fixes on top
- Using explicitely DIRACOS v1r20
DIRAC projects
DIRAC:
Issues by milestone:
PRs discussed:
- just briefly discussed some of the open PRs.
WebApp:
- Merged 2 small PRs for fixes
- Preparing for pip package. PR is almost ready to be merged. Not yet publishing to pypi, will do later.
Pilot3:
- Daniela https://github.com/DIRACGrid/Pilot/pull/129 (fairly large update to pilot code): It didn’t break anything (this time?) but should this have tags so we can pull specific versions ?
- maybe use a commit hash?
- for pulling specific version there should be already the option, but not so trivial
devel branch to be actually used, e.g. in certification?
DIRACOS:
xroot5?
arc6
- created a v1r19 and tested in DIRAC certification. Looked OK, but v1r20 had to be created anyway for other issues with the SQLAlchemy version. This was done.
condor 8.8?
- Marko tried several times to have it working. Several dependencies needed.
DIRACOS2:
- from previous meeting
fts-rest on py3?
- from previous meeting Question for
rucio client… (issue)?
- N else TR
VMDIRAC:
- Using Pilot/Version instead of Cloud/Version
Documentation:
OAuth2:
tornado/HTTPs
management
- from previous meeting 1 task left for deploying on CVMFS
COMDIRAC
other externals, including Rucio
- PR: https://github.com/DIRACGrid/DIRAC/pull/5067
- failing tests
- no updates since last time
- from previous meeting Janusz I tried integrating in our setup. Didn’t try the agents.
- configuration: Rucio insists on having a config file, but all these configs should (could) be put in DIRAC CS. We should insist on Rucio to not needing this config file.
Release planning, tests and certification
-
Certification machine
-
Next hackathon
Weekly development(s) focus
NTR
AOB and topics from Google forum
- DUW in less then 3 weeks
- Timetable is shaping: https://indico.cern.ch/event/852597/timetable/#all.detailed
- Monday: “developments” sessions
- Tuesday: “experiment reports” session. Prepare your pres, answer the pre-set questions and add whatever content you want. 15min + 5.
- Igor I would like to ask 2 more questions:
- number of jobs ran in the last 2 years.
- CPU (or Wall) time used by jobs in the last 2 years.
Next hackathon on April 29th:
Next BiLD on May 06th: https://indico.cern.ch/event/1032098
LHCbDIRAC