Technical Coordination Weekly

Europe/Stockholm
Skype

Skype

Balazs Konya (Lunds universitet)
Description
Technical coordination group members and invited persons

12 September 2017 14:05 - 14:55

Present: Balazs, Maiken, Mattias, Anders, Aleksandr, Oxana
Apologies: David

== News

There's an interest for ARC roadmap and development plans, we should keep it up-to-date in a way comprehensible for 3rd-party. Conference slides and such need to be converted in some understandable plans, including release plans.  

Maiken will talk about our infosys approach to ATLAS next week. Balazs adds that ATLAS' new CRIC infosys solution ran into some problems with queues, esp. in the Condor glide-in context, and also has problems fitting other experiments.

Abdulrahman is planning to investigate aCT as a metascheduler in the context of Supercomputing BoF, would like to have help from some ARC experts, but nobody seems to be traveling.

Nightly builds are affected by a faulty disc, Anders is investigating. Fixing bad signature of Debian packages in NG repo is a non-trivial issue.Mail server has moved, perhaps Bugzilla will move as well. DNS record for Archery will be solved if there will be a Bugzilla request (Balazs will submit it).

Aleksandr has a working REST interface, stuck with documentation
 

== Release

5.4.0rc is installed in Oslo, will be installed at NSC and in Ljubljana, so far so good. Florido considers porting some fixes still, unclear whether it is critical (if it is about negative jobs, then it might be acceptable), Maiken will investigate. Seems like Aleksandr already fixed bug #3678.

Jozef offered support for release testing, Balazs thinks that the old test definitions (~20 cases) can be resurrected. 


== Bugs

##3673 - 3676 still need to be read by Martin. Aleksandr promises to resolve as fixed #3655.


== A.O.B.

Status of the next technical meeting in Ljubljana is still unclear

There are minutes attached to this event. Show them.
    • 14:00 14:20
      News 20m
      ARC-related news from various activities
    • 14:20 14:30
      Actions follow-up 10m
      Follow-up on actions defined at the previous meeting
    • 14:30 14:50
      Release status 20m
      Coming release status
    • 14:50 15:20
      Bugs 30m
      New bugs since previous meeting, as well as blockers and critical ones
    • 15:20 15:30
      A.O.B. 10m