At CERN: Federico, Christophe, Zoltan, Joel, Andre', Marko, Hamza
On Vidyo: Marcelo, Wojtek,

Apologies: Daniela, Simon

Follow-up from previous meeting

• NTR

Current situation

• v6r19p11 is the last production version
  • One fix for Sandboxes cleaning: we discovered that old sandboxes that failed to be cleaned were not re-tried, so stayed forever.
  • Anyway FTSAgent is buggy, fixed in a PR 

WebApp:

• The new release procedure of WebApp has been merged, will be part of v6r20
  • Documentation needs to be updated 

Pilot:

• NTR

Externals:

• NTR
• Need to add a python library for v6r20 [Chris]

LCG bundles:

• v13r0 includes python packages like pyparsing and futures, which should be anyway in the externals. To verify
• still not moved its "development" to GitHub. This would also answer the recurrent question of the content of each release

REST:

• Wojtek will create PRs as soon as possible for:
  • choosing among different authentication methods (OAuth and X509)
  • adding the pilots logging interface
  • Delayed because of issues discovered in the DIRAC stomp interface
  • ...and because of code refurbishment
• The connection with CS-based authZ will be done later
• Tornado proposes some unit/integration tests which look easy to use, and that can be integrated in Travis or Jenkins. Maybe also for WebApp.  

BOINC:

• NTR, docs still need to be completed

PyGSI:

• NTR

Documentation

• NTR

DB12:

• NTR

Release planning, tests and certification

Release planning:

• v6r19 series
  • v6r19p12 should be out today or tomorrow
• v6r20 series
  • pre10 out
  • several PRs need to be reviewed
  • the changes in REST, once done and merged, will be included in a pre-release, which we can then install on the DIRAC certification machine

Certification process: 

• v6r20 certification: 
  • Using trello and slack as usual, not much progress these last 2 months

Weekly development(s) focus

• Move to Web API
  • We want to move from dips: to https: for our services
    • URLs with static part, and a variable part that explains which handler to use
      • no need for specifying ports
  • Building blocks:
    • tornado
    • JSON (RPC?)
  • We want:
    • AuthN based on openSSL (using env variable for RFC proxies)
    • AuthZ same as now
    • remove typing
  • First step: JSON
    • In several steps
    • PRs #3585 and #3586
      • Need further reviews, and if OK and not disruptive it can go also in v6r20 

DIRAC: current PRs and tasks being worked on

• FTS3 PR needs more review

DIRAC communities roundtable

• ILC: NTR
• LHCb: NTR

AOB

• Next BiLD-Dev meeting will be held in 3 weeks (February 8)

LHCbDIRAC

• We should right now concentrate on testing v6r20
  • And then we decide what to base v9r2 on