BiLD-Dev

→ Europe/Zurich
Federico Stagni (Conseil Europeen Recherche Nucl. (CERN)-Unknown-Unknown)
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) – 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

CLIC:

 André

  • NTR

LHCb:

 Federico+Chris+Chris+Marko

  • Nothing interesting to report

EGI + France Grilles:

 Andrei

  • Users started to submit long jobs (longer than the VOMS extension). This is an issue at the moment as the payload renewal inside the CE was failing (M2Crypto error message). Issue created: https://github.com/DIRACGrid/DIRAC/issues/5114. Asked VOMS to increase the default length, but for the moment put back a pre-M2Crypto version

  •  André ARC Information not in BDII (glue2): example ticket https://ggus.eu/index.php?mode=ticket_info&ticket_id=150495 with that problem at KEK, where they had to fix something in the ARC system

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.
    •  Hideki not that I know

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

DIRAC releases

  • v7r1p38:
    • Just fixes
  • *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:

  • v7r1:
    • A few more issues have been added lately
  • v7r2:
    • NTR
  • v7r3:
    • NTR

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?
    • NTR
  • 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 meetingfts-rest on py3?
    • NTR
  • from previous meeting Question for rucio client… (issue)?
    • NTR
  • N else TR

VMDIRAC:

  • Using Pilot/Version instead of Cloud/Version

Documentation:

  • NTR

OAuth2:

tornado/HTTPs

  • NTR

management

  • from previous meeting 1 task left for deploying on CVMFS
    • Not yet done

COMDIRAC

  • NTR

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

    • next week (29th April)
      • v7r3-preX

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

There are minutes attached to this event. Show them.