Skip to content

Conference call notes 20190403

Kenneth Hoste edited this page Apr 3, 2019 · 2 revisions

(back to Conference calls)

Notes on the 122nd EasyBuild conference call, Wednesday Apr 3rd 2019 (17:00 - 18:00 CEST)

Attendees

Alphabetical list of attendees (7):

  • Damian Alvarez (JSC, Germany)
  • Fotis Georgatos (SDSC, Switzerland)
  • Bart Oldeman (ComputeCanada)
  • Victor Holanda (CSCS)
  • Kenneth Hoste (HPC-UGent)
  • Åke Sandgren (Umeå University, Sweden)
  • Davide Vanzo (Vanderbilt University)

Agenda

  • outlook to EasyBuild v3.9.0
  • update on progress towards support for "eb --remove"
  • the road towards EasyBuild 4.0
  • Q&A

Outlook to EasyBuild v3.9.0

Update on progress towards support for "eb --remove"

  • first step for a (safe) implementation of "eb --remove" is to be able to determine reverse dependencies

  • will not be ready for EasyBuild v3.9.0 (hopefully by EasyBuild 4.0)

The road to EasyBuild v4.0

Q&A

  • Bart: how many packages use MPI version of FFTW?

    • only PETSc?
    • Åke: also VASP
    • Victor: GROMACS too? (Bart: no)
    • FFTW wrappers in MKL requires MPI
    • could consider removing FFTW MPI from toolchain?
      • separate FFTW-MPI as dependency where needed
    • worth considering for 2019b generation of easyconfigs?
      • which would be first common toolchain version in EasyBuild v4.0
    • should check whether this has impact on framework w.r.t. toolchain build env prepare
  • Victor: flex/Bison deps for binutils is a bit of a mess

    • different versions, no longer needed since they're only build deps for build deps
    • unclear why they are needed, pollute user environment
    • Kenneth: done because of bootstrapping, to shield ourselves from the OS
    • Åke: could introduce the concept of bootstrap-only build dependency that are trashed after use
  • Victor: support for containerize to have layered builds

    • helps a lot with getting minimal container images
    • not supported yet in eb --containerize, but since now both Singularity & Docker has this, it's interesting...
  • issues will be opened in framework repo for each of these to follow up...

Clone this wiki locally