At CERN: Zoltan, Christophe, Andre', Louis, Vladimir
On Vidyo: Federico, Xiaomei, Wojtek, Yash, Daniela, Simon, Marcelo

Apologies: Andrei

Follow-up from previous meeting

• DUW 4 weeks ago
  • feedbacks in https://docs.google.com/forms/d/1C67pOX0UwulLsh-LZeDFq4IaJlmcCmRlTSqtYmTSdeM/
• PR (#3713) for fixing the infamous "invalid action proposal" by speeding up the handshake and not looking up the user/group in the baseStub: backported to v6r19, working as expected. In production for many now.
• does the OSCompatibility section in CS need to be kept up-to-date? Not sure, to be checked.
•  

Current situation

DIRAC

• v6r20p3 out
  • used in test from CLIC and GridPP and LHCb
• v6r21-pre1 out
  • in DIRAC certification

WebApp:

• v4r0 looks "ready", won't depend from any specific DIRAC release
  • ready to be merged and to be part of DIRAC v6r21

Pilot3:

• Wijtech working on tests in Jenkins

Externals:

• NTR

DIRACOS:

• pushed to https://github.com/DIRACGrid/DIRACOS the first version
• checked by Marcelo
  • some documentation unclear/missing
  • once done a new tested (proposed Marko) will try it one more time
• ready to be used already for v6r21
  • needs some changes in dirac-install script

LCG bundles:

• v14r2 created. Includes new versions of fts3, gfal2
  • Now the "official" version to be used in v6r20
• CC7 version does not include M2Crypto [to be fixed still]

REST:

• NTR  

BOINC:

• NTR, docs still need to be completed

PyGSI:

• NTR

Documentation

• At the DUW we agreed on putting more technical info in the docstrings of the DIRAC components
  • Andre' has added in PR #3723 the technical documentation to start/administer two TS agents. 
  • Anyway we agreed to not use the tabular format, but rather to add some snippets of the CS
  • This PR will "set the tone (the format)" on how to write this technical documentation.

DB12:

• NTR

Release planning, tests and certification

Release planning:

• v6r19 series
  • NTR (just a patch coming)
• v6r20 series
  • v6r20p3 created today, ready for v6r20p4
    • #3726, #3725, #3722
• v6r21 series
  • v6r21-pre1 is out
  • for this series, we agreed that DIRACOS will be used
  • also WebApp 4.0 can be used
  • this takes us to name this release v7r0
  • the list of feature request is already getting closed

Certification process: 

• v6r21 certification: 
  • v6r21-pre1 installed already in DIRAC certification setup
  • https://jenkins-dirac.web.cern.ch/ is open to registrations for who needs it or wants it

Weekly development(s) focus

• dirac-install ++ follow-up
  • based on task #3517
  • ongoing PR: #3678
  • we need to be careful to keep the backward compatibility, as many instructions point to use the version found in integration branch.

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

• PRs:
  • #3703 on new production system: several comments, not for today (Luisa not present). Won't be merged, for now
  • #3724: can be merged anyway, the actual deployment should anyway be done by hand (DB operation)
  • #3723: Multi-VO transformation system. Not much code, actually. No need for changes at the DB level 
• Forum:
  • GridPP installing the transformation system. Quite some work to actually fix the CS correctly. Interested in #3273.

DIRAC communities roundtable

• BES: 
  • Moving to v6r20 next week
• CLIC:
  • mostly testing multiVO TS
• LHCb: 
  • NTR

AOB

• Next BiLD-Dev meeting will be held in 2 weeks (July 5) just before CHEP

LHCbDIRAC

• Louis work is ongoing, a prototype will be soon possible
  • ready to be presented at BiLD in 2 weeks, need some decisions
  • tornado now compatible with proxies
    • Chris worked both on tornado and on M2Crypto side
• v9r2 certification
  • progressing, one more round just started:
    • Chris submitted a staging transformation that showed few issues, PR coming today
    • not yet installed on CVMFS
      • we need to keep the "old way" of installing because anyway this https://its.cern.ch/jira/browse/LBCORE-1410 is not completed
        • would need to restart discussion just after CHEP
    • possible to deploy the week just after CHEP