BiLD-Dev

→ Europe/Zurich
2-R-014 (CERN)

2-R-014

CERN

Federico Stagni (Conseil Europeen Recherche Nucl. (CERN)-Unknown-Unknown)
Description
Bi-Weekly "Loyal" DIRAC developers meeting. And, following, the LHCbDIRAC developers meeting.

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

Apologies: Andrei

 

Follow-up from previous meeting

  • Glue2 support added in v6r19
    • works "fine", for all resources advertised, but CERN recently changed something in what they publish, so now it doesn't update the OS correctly -- the OS is in the CE section in the CS, while it should maybe be in the Queue sub-section 

Current situation

DIRAC

  • NTR

WebApp:

  • a couple PRs to be merged
  • v4r0 looks "ready", won't depend from any specific DIRAC release

Pilot:

  • Pilot3 is optional for v6r20 SiteDirectors, using a flag
    • Not tested yet. What's tested is that Pilot2 are still submitted.
    • Currently Pilot3 files are uploaded to the web portal

Externals:

  • NTR

LCG bundles:

  • v14r1 in testing
    • All looks OK for SLC6
    • CC7 version does not include M2Crypto [to be fixed still]
  • current production version is still v13r0
  • DIRACOS: minor progress
    • its repo will be moved to Github

REST:

  • NTR  

BOINC:

  • NTR, docs still need to be completed

PyGSI:

  • NTR

Documentation

  • Several documentations updated
    • Zoltan reports that accounting documentation also needs an update

DB12:

  • NTR

Release planning, tests and certification

Release planning:

  • v6r19 series
    • NTR
  • v6r20 series
    • Should be ready ASAP
    • FTS3 monitoring was forgotten, included now
      • still some issues that Chris will address ASAP

Certification process: 

  • v6r20 certification: 
    • Last checks ongoing, Andrei found few more issues to address

Weekly development(s) focus

  • A discussion arised about:
    • if the OS in Resources/Sites/CE section is used or not: Federico thinks not
    • if the OSCompatibility section needs to be kept updated
      • probably yes, but not sure for vanilla DIRAC, need to re-check

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

  • NTR

DIRAC communities roundtable

  • GridPP:
    • [see pdf attached]: issues with "invalid proposal" errors increasing with number of users
    • a solution is coded, but imperfect as of now
      • It would speed up things considerably, but ForwardDISET operations would fail
      • Simon and Chris will look at it during the workshop next week
  • BES: 
    • NTR
  • ILC:
    • NTR
  • LHCb: 
    • NTR
  • DIRAC4EGI:
    • NTR
  • Belle2:
    • NTR
  • CNAF:
    • NTR

AOB

  • Yash joined as GSOC, just started this week
    • in addition to the project's goal (use ElasticSearch for Job Parameters), he wants to make sure that the code written will be python3 compatible
  • DUW agenda final
    • always bring your ID with you
    • we can't be there before 8 nor after 18:20
      • one of the themes will be for how to handle productions
        • and hopefully coming out with a common plan
        • Luisa created an RFC and would like to discuss it
      • another theme will be data management for the experiments
        • there will also be a presentation from Rucio
          • we just need to prepare for possible integration questions (not suggested and not supported)
      • Ops hackathons being planned
        • One will be a TS hands-on
        • Various users being contacted
  • Next BiLD-Dev meeting will be held in 3 weeks (June 7)

LHCbDIRAC

  • Nothing specific To Report
  • Louis work is ongoing, mostly right now is about understanding DIRAC's internals
    • tornado not compatible with proxies yet -- due to an SSL "missing feature"
    •  Chris opened an issue on tornado github, for using M2Crypto (they agree, but no immediate reaction)

 

There are minutes attached to this event. Show them.