BiLD (Bi-weekly DIRAC Development meeting) – 31/03/2022

At CERN (in our offices) Federico, Alexandre, André, Christophe
On Zoom: Andrei, Daniela, Janusz, Simon, Hideki, Michel Hernandez Villanueva
Apologies:

Follow-up from previous meetings

• hackathon of March 24th, on 8.0.0a18: https://trello.com/b/ohM58Vyf/v800a18
  • installation issues (resolved)
  • WMS issues (prob not solved)

DIRAC communities roundtable

GridPP:

Daniela+Simon+Janusz

• We now have one development server running v7.3 in python3. It mostly works, the rest will show up as issues/discussion/or if I don’t want Chris H to see it, the mailing list :-)
• Simon would really like a v7r2p43 release (for the unicode fix)

LHCb:

Federico+Christophe+Alexandre

• NTR

EGI:

Andrei

• installed one server with py3 (7.3)
• trying ES

ILC/CLIC/FCC:

André

• NTR

Belle2

Hideki

• Mostly some questions. Still running v7r1 in production.

Topics from GitHub/Discussions or Google forum

• Problems with CI tests
  • not sure what to do, as we can’t start fixing each and every package version.
• HTCondor CE plans to end support for X509 in November
  • answered
• PilotSyncAgent fails to sync pilot files to web server
  • answered, but there might be different solutions.
• diracos2/libcloud/conda forge
  • the suggestion is to start by contacting the maintainers of the package on conda-forge (making an issue in GitHub), or take over.

DIRAC releases

• v7r2:
  • No new releases made (but should)
• v7.3:
  • No new releases made (but should, as there are quite some changes)
• 8.0.0a18:
  • NEW: (#5974) TornadoMonitoring handler
  • CHANGE: (#5965) removed gMonitor
  • FIX: (#5941) dirac-login uses the correct proxy to add VOMS attributes

DIRAC projects

DIRAC:

Issues by milestone:

• v7r2:
  • PR [v7r2] added op_type option in elasticsearch options for fixing #5920 (failing tests)
• v7r3:
  • Closed Jobs with “impossible” logging info
• v8.0:
  • ComponentMonitoring issues in DIRAC web app and ES
    • some updates
• v8.1:
  • NTR

Other issues:

• NTR

PRs discussed:

• [7.3 and up] Introduce a CloudComputingElement: (https://github.com/DIRACGrid/DIRAC/pull/5988)
  • goal is to replace CloudDirector and use SiteDirector for grid and cloud
  • conceptually treat a VM as a pilot job (use instance id as pilot job reference)
  • python3 only as it depends on a version of apache-libcloud (>= 3.4.0) that is only released in python3 (if you want to use appcred)
  • old VMDIRAC components should be unaffected (mark as deprecated in v8 ?)
  • we tried some basic cases, but would like to work with users (Andrei) to make sure it works on FedCloud and elsewhere
  • Andrei we tried to use libcloud long time ago and failed (too many dependencies). Does it support tokens?
    • not sure
  • Andrei+Federico we need to make sure that the project is maintained before committing to it
    • Simon I think the support is pretty OK (the maintainers are active). The tokens should be OK.
    • OpenNebula might be broken, no way to test atm.

WebApp:

• Some PRs open for 5.0 (counterparts of open ones in DIRAC)

Pilot:

• Janusz server PR restructured a bit, e.g. using standard DIRAC loading mechanism. The ElasticSearch backend has not been added yet (only the file backend)
• Janusz client: the current system of RemoteLogging is too complex. The suggestion from Chris Burr to capure the outputs in the pilot wrapper look much simpler, investigating that and trying different options.
  • Federico remember that the PilotWrapper created in DIRAC is only used by the SiteDirectors, e.g. not by Cloud yet. This might change with the new PR #5988 (to check)

DIRACOS2:

• NTR

Documentation:

• from previous meeting diracgrid.org still forwards to http://mardirac.in2p3.fr

OAuth2:

• from previous meeting Any news from issue WLCG and Token transition – reminders and requirements ?
  • NTR

tornado/HTTPs

• from previous meeting Andrii We can eventually have special classes in Configuration and BundleDelivery to pass binary data - to be discussed.
  • NTR

management

• NTR

diraccfg

• NTR

COMDIRAC

• NTR

DB12

• NTR

Rucio

• PR merged, what’s next?
  • Janusz we have to find some users, will need to write instructions on how to use it

Development focus

• planning to replace Executors with Celery (https://docs.celeryq.dev/en/stable)
  • a student starting next week. Looks promising but we need to gain experience
  • we are looking to replace the Executors machinery that runs the Optimizers (the Optimizers would stay)
  • No DB changes ahead
  • will need to use RabbitMQ as backend
  • internal note if anyone’s interested: https://codimd.web.cern.ch/hP0589uFT4CLam5Kv2Yfhg#

Release planning, tests and certification

• 8.0 release

  • Currently missing:
    • a few critical issues, but for OAuthZ we don’t want to improve ATM
    • BLOB->TEXT everywhere (only 1 DB missing)
  • Not in a hurry to have the release out. Target: 3/4 more weeks.

• Certification machines

  • lbcertifdirac70 machine:
    • NTR
  • lbcertifdiracoauth machine:
    • NTR

• Next hackathon(s)

  • Still on lbcertifdirac70

AOB

Next hackathon on April 7th
Next BiLD on April

from previous meeting consortium agreement) Will go through another round.

from previous meeting DIRAC Workshop. 9-10 May 2022. Will stay virtual, and the presentations will stay in the mornings (similar schedule to last years’). The question is if we want to ALSO meet at CERN, and add non-ZOOM sessions in the afternoons.

---

LHCbDIRAC

• v10r3: deploy board in https://trello.com/b/kzUKdMts/deploy-v10r3
  • lbwms: considerations in https://codimd.web.cern.ch/5-ImZHjFTi6ko_a-5-5BFw#
• LHCbDIRAC hackathon based on 8.0
  • can start looking into it, target second week of April
• Started to use MareNostrum, still some issues, slowly fixing (100 concurrently running jobs at the moment)