Go to the Indico Home Page Oldest event Older event Up to category Newer event Newest event Printable version
 
Focus on:  Hide Contributions
  • Compact style
  • Indico style
  • Indico style - inline minutes
  • Indico style - numbered
  • Indico style - numbered + minutes
  • Indico Weeks View
    • Switch to the management area of this event
    Login

    BiLD-Dev

    → Europe/Zurich
    Federico Stagni (Conseil Europeen Recherche Nucl. (CERN)-Unknown-Unknown)
    Description

    Bi-Weekly "Loyal" DIRAC developers meeting. And, following, the LHCbDIRAC developers meeting.

    Join Zoom Meeting
    https://cern.zoom.us/j/91857549918?pwd=S2c1ZmFpYVNDOGk4YjMrZmhOeGROUT09

    Meeting ID: 918 5754 9918
    One tap mobile
    +41315280988,,91857549918# Switzerland
    +41432107042,,91857549918# Switzerland

    Dial by your location
            +41 31 528 09 88 Switzerland
            +41 43 210 70 42 Switzerland
            +41 43 210 71 08 Switzerland
            +33 1 7037 2246 France
            +33 1 7037 9729 France
            +33 1 8699 5831 France
    Meeting ID: 918 5754 9918
    Find your local number: https://cern.zoom.us/u/aUn2ex94J

    Join by SIP
    91857549918@188.184.110.70
    91857549918@188.184.89.188

    Join by H.323
    188.184.110.70
    188.184.89.188
    Meeting ID: 918 5754 9918
     

    working notes
    Hide

    BiLD (Bi-weekly DIRAC Development meeting) – 03/12/2020

    At CERN: Again, nobody :/
    On Zoom: Federico, Alexandre, André, Andrei, Andrii, Cedric, Christophe, Christopher, Daniela, Janusz, Marko, Simon, Xiaomei

    Apologies:

    Follow-up from previous meeting

    • Ran hackathon last week on v7r2-pre22:

      • indico + trello
      • added EnableActivityMonitoring option to REA (using MonitoringSystem)
        • not tested yet
      • https functionalities not yet tried out
      • Release not complete

    • M2Cryto and pyGSI compatibility: there should not be any incompatibility. Right now this is solved but not understood.

    DIRAC communities roundtable

    GridPP:

     Daniela

    • No major updates
    • Problems when diracproject.web.cern.ch went down, this was seen by many VOs.
    • Deploying gridPP UI on CVMFS

    CLIC:

     André

    • NTR

    LHCb:

     Federico

    • Still on v7r0, could not do proper hackathons. Waiting for new v7r1 patch.

    EGI:

     Andrei

    • NTR

    France Grilles:

     Andrei

    • NTR

    Belle2:

     Cedric

    • NTR

    JINR

     nobody

    • NTR

    Juno, BES3:

     Xiaomei

    • Juno migrating to CentOS7.8
      • found that package boost_python missing in DIRACOS
      •  Marko in DIRACOS there’s boost 1.41, are you in the wrong environment?
      •  Christopher it should be using only things from DIRACOS, please open an issue to DIRACOS
      •  Federico it’s v6r22, maybe it’s an old version?
        • try using a newer version of DIRACOS, but you need to pay attention to the possible incompatibilities (e.g. xroot)
        •  André we are using v6r22 with DIRACOS v1r11

    DIRAC releases

    • v7r0p41:
      • Mostly minor fixes
    • v7r1p20 + v7r1p21:
      • Fix singularityCE (hopefully last time)
      • Fix bug in handling the bulk status updates that was not updating correctly the job status
    • v7r2-pre23:
      • Several fixes, including v4r2 WebApp version.

    DIRAC projects

    DIRAC:

    PRs

    • Fix JobWrapper and job StartTime pretty dense PR, some necessary fixes for v7r1
      • need careful review
    • nginx upload files
      •  Andrii I still need to add a test, I will do it ASAP
      •  Andrei Can we use DIRAC SE for storing these file
        •  Christophe I think this should be a sysadmin task, and so done by sysadmin tools.
        • Nothing prevents us to have several ways of storing these files, so we can maybe add another way
        • In any case, it should be done asynchronously (right now we use the CS)

    Issues

    • Environment Isolation follow-up, updates?

      •  Daniela Sorry, I forgot, as far as GridPP is concerned it seems to work for us.
      •  Christopher I updated the list of tasks in it, the last 2 are still valid but not anymore important

    • v7r0:

      • 1 HTCondor issue  Alexandre

    • v7r1:

      • Still some tasks in there, some are for documentation
        • proxyManagement documentation in PR

    • v7r2:

      • mostly non-urgent ones

    • v7r3:

      • Not discussed

    WebApp:

    PRs

    Merged v4r2 PRs for:

    • use dirac.cfg instead of web.cfg
    • use nginx+webdav plugin for uploading files to web portal
      • instructions changed, be careful

    Issues

    • Closed several old issues

    Pilot3:

    PRs

    • Merged https://github.com/DIRACGrid/Pilot/pull/121:
      • Added possibility to bind the WN to a VO (for multi-VO when using certificates)
        • option should be used in VMDIRAC
      • Added --cfg for newer releases, based on a hard-coded version of DIRAC
      • For extensions you can override the version

    Issues

    DIRACOS:

    •  Marko: the master branch is broken because SLC6 is being archived, looking how to fix it
    • xroot5? is it needed?
      • not in the immediate
    •  Federico out of the issues in https://github.com/DIRACGrid/DIRACOS/issues which one will have a follow-up?
      •  Christophe I will close some of them

    DIRACOS2:

    • See below discussions for python3

    VMDIRAC:

    • Simon agreed on being the maintainer of this package
    •  Federico Some maintenance is needed:
      • tests
      • automation of tests
      • python3 code

    Documentation:

    OAuth2:

    • WIP

    tornado/HTTPs

    • NTR

    management

    diraccfg

    • NTR

    other externals, including Rucio

    •  Cedric: I think we should have Rucio adopting DIRAC convention, not the contrary

    PRs

    • Janusz added https://github.com/DIRACGrid/DIRAC/pull/4837 for discussion
      •  Christophe we should use the python client, not the REST API
      • we need to sort out the cfg issue
      •  Cedric: all parameters will be passed in the constructor but I won’t have time to work on it until mid of January, so news in February

    Release planning, tests and certification

    Weekly development(s) focus

    • On the usage of exceptions old topic that routinely comes up

      • In summary: exceptions are fine as long as they are in a “confined” environment

    • Ideas for integrating DIRAC with setuptools

      • Christopher did the main work, discussed already with Christophe and André.
      • See https://www.notion.so/Ideas-for-integrating-DIRAC-with-setuptools-106d461ad8fb444d96300a4c7b6d7cf8 for all the ideas
        • everthing that’s proposed is for python3 DIRAC
          • maybe it would work also for python2, but we don’t know which effort would be required, and won’t investigate that: we basically keep things as they are for python2
        • releases.cfg is a source of possible errors, and won’t be needed if things are implemented correctly
        • on changing the version numbers:
          •  Andrei there’s nothing specific against it
            • what is there is for historical reasons
        • repository layout: fine, go ahead ~now
          • but need to update the dirac-distribution to consider also this possible layout
        • extensions discovery: can be done by using entry_points, and a priority.
        • it should be possible to use pip also for further configuarations, thus avoiding the need for dirac-configure for client installations.
      • targeting which release? (is there a release to target?)
        • the simple changes can go in already (v7r2) and the rest will come

    AOB and topics from Google forum

    Next hackathon in 1 week (last of 2020).
    Next BiLD in 2 weeks (last of 2020).

    LHCbDIRAC

    • Prob hackthon tomorrow afternoon
    There are minutes attached to this event. Show them.