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, Christophe, Marko, Zoltan, Philippe, Joel, Andrew, Milosz, Hamza
On Vidyo: Xiaomei, Daniela 

Apologies: Luisa

 

Follow-up from previous meeting

  • RFC proxies are now the default in v6r19
    • Then we can remove old legacy code in future versions (m2Crypto simplifications)
  • TranformationDB on cluster (MariaDB galera cluster with 3 nodes), triple increase of auto-increment
    • Verified, no code issues (was missing a trigger on their side)
  • lcgBundle repo not created

Current situation

DIRAC:

  • v6r19 is the last production version
    • very long list of changes in https://raw.githubusercontent.com/DIRACGrid/DIRAC/integration/release.notes
      • logging based on python standard logging: Marko P. to verify some possible inconsistencies
      • new RSS rewritten in many parts, now including every type of resource
      • Adapting to MySQL 5.7
      • New network accounting (discussion if it should be monitoring instead)
      • The application error codes, when returned, are passed to the JobWrapper, and maybe interpreted.
      • The JobWrapperTemplate can reschedule a job if the payload exits with status DErrno.EWMSRESC & 255 (222)
      • and many others
    • branch rel-v6r19 also created
    • Due to lcgBundle issues, we won't assure any working version for CC7
      • lcgBundle v13r0 to be used in conjunction

WebApp:

  • NTR

Pilot:

  • NTR
  • We can introduce Pilot3 as optional from the SiteDirectors from next version (v6r21?)

Externals:

  • NTR

LCG bundles:

  • Version v13r0 looks OK, but not CC7 version, which is NOT for this meeting
    • DIRAC v6r19 depends from that
    • This version includes python packages like pyparsing and futures, which should be anyway in the externals. To verify

REST:

  • NTR, but Chris could not manage to use it. Broken?

BOINC:

  • NTR

PyGSI:

  • NTR

Release planning, tests and certification

Release planning:

  • v6r17 series
    • NTR
  • v6r19 series
    • v6r19p1 should be out ASAP
  • v6r20 series
    • Decided to include:
      • https://github.com/DIRACGrid/DIRAC/pull/3434 (removing old Web fully)
      • https://github.com/DIRACGrid/DIRAC/pull/3486 (Pilots Logging system)
        • IFF there's a flag for enabling it or not

Certification process

  • v6r20 certification is ongoing: 
    • Using trello and slack as usual
    • Also ILC people in
    • Already asked to create v6r20-pre2
  • The lhcb-jenkins server needs to be retired soon, we need to find a solution ASAP

Weekly development(s) focus

  • Chris wanted to discuss our development strategy, but we decided to postpone it to a dedicated meeting

DIRAC: current PRs and tasks being worked on

  • pyGSI -> M2Crypto: maybe for v6r21
    • still lacking the sockets part

DIRAC communities roundtable

  • ILC: moved smoothly to DIRAC v6r17
  • GridPP: NTR
  • BES3: NTR

AOB

  • Reviewer settings in DIRAC should allow also non-owners to be proper reviewers
  • Next BiLD-Dev meeting will be held in 2 weeks (October 26)

 

LHCbDIRAC

  • All tasks for migration out of lb-run have been added to https://its.cern.ch/jira/browse/LBCORE-1410
    • Need to be done with order (some dependencies there, e.g. LHCbDIRAC changes first require changes in Core SW)
  • We can put lb-run -c best LHCbDIRAC now in pilots, as last releases are OK (only releases for gcc49)
    • Pilot 3 first (HLT farm as tester)
  • Release v9r0 feature list is closed, all other MRs will go in v9r1
    • Possible release on October 23rd
  • QT4 -> QT5? Progress? Urgency?
There are minutes attached to this event. Show them.