At CERN: Federico, Christophe, Zoltan, Andre' Marko
On Vidyo: Xiaomei, Daniela, Simon, Wojtek, Jiri

Apologies: Andrei, Luisa

Follow-up from previous meeting

• Next DIRAC Users Workshop: confirmed in London, hosted by Imperial College. 13 - 17 May 2019 (Tuesday to Friday)
  • Main presentations in a hotel close to the college
    • secondary room in Imperial College
  • Fee of 80 GBP
  • https://indico.cern.ch/event/DUW9
    • Will announce to the forum as soon as some info there are corrected (e.g. venue)
• last meeting was dedicated to HTTPS
  • Big PR made, should not be making any issue to current code if merged
  • Can probably be merged
• python3 workplan: thread to revive, not too urgent

DIRAC communities roundtable

• BES: 
  • NTR
• CLIC:
  • Agent adding some monitoring info (e.g. what's started/stopped on a machine) developed for CLIC, probably making a PR for evaluation
  • Logging: experiencing with filters
• LHCb: 
  • Looking into using parametric jobs in production
  • MP queues: hopefully deploying a few
• GridPP:
  • question on the forum about umask returned by DFC: Chris will look into it and answer
  • #3802 blocking update of DIRAC version (stuck at v6r20p9). What to do?
    • answer: no changes to Externals will be done. Need a "hack" fix, via PR. Code in current PR not yet correct
• Jiri asked if anyone use IRODS... apparently no-one.

Current situation

DIRAC

• v6r20p13 out
  • mostly fixes, especially for parametric jobs
  • https://github.com/DIRACGrid/DIRAC/issues/3828 for addressing possible bug introduced in PR 3814 (which was merged in v6r12)

WebApp:

• NTR

Pilot3:

• NTR
• Wojtek says that for pilots logging, the pilot part is ready

Externals + LcgBundle:

• No more upgrades, all efforts going to DIRACOS

DIRACOS:

• Marko:
  • Tarball created daily and uploaded to cern.ch/diracos
  • There was an issue with EPEL repository now solved
  • More testing added

REST:

• NTR, probably getting fully discontinued by move to HTTPS

BOINC:

• NTR

PyGSI:

• NTR, efforts are now going into properly integrating M2Crypto

Documentation

• See #3763 for example on how to use the ConfigTemplate.cfg for documenting the DIRAC components

DB12:

• NTR

Release planning, tests and certification

Release planning:

• v6r20 series
  • NTR
• v7r0 series
  • the list of feature request is already closed
  • Almost all the PRs can be merged, after proper review
  • There are already integration tests in Jenkins that use DIRACOS, and they are OK
    • What's missing are some changes to dirac-install for specifying where to get the tarball from

Certification process: 

• v7r0 certification:
  • NTR
• https://jenkins-dirac.web.cern.ch/ is open to registrations for who needs it or wants it
  • Luisa used it to verify ProductionSystem integration tests

Weekly development(s) focus

Nothing specific, mostly medium term planning

• M2Crypto is necessary, Chris has wrote many unit tests.
  • A PR will come, and will need to be for v7r0
  • for v7r0 we plan to have it as technology preview (with a environment variable)
• The PR Chris made to tornado for using M2Crypto is still under discussion
• HTTPS PR can be merged, but right now good part of the code will stay unused (pending the 2 bullets above)
  • we are talking about doing something real not before v7r2)

DIRAC: current PRs and tasks being worked on, or topics from Google forum

• NTR (already discussed)

AOB

• Next BiLD-Dev meeting will be held in 3 weeks

LHCbDIRAC

• v9r3 plan in the wiki
  • Won't be possible to deploy in September
• v9r3 can probably be deployed using the lcgBundle (NOT LHCbGrid anymore)