Skip to content

Conference call notes 20190501

Åke Sandgren edited this page May 1, 2019 · 3 revisions

(back to Conference calls)

Notes on the 123rd EasyBuild conference call, Wednesday May 1st 2019 (17:00 - 18:00 CEST)

Attendees

Alphabetical list of attendees (6):

  • Fotis Georgatos (SDSC, Switzerland)
  • Kenneth Hoste (HPC-UGent)
  • Mikael Öhman (Chalmers, Sweden)
  • Bart Oldeman (ComputeCanada)
  • Åke Sandgren (Umeå University, Sweden)
  • Davide Vanzo (Vanderbilt University)

Agenda

  • outlook to EasyBuild v3.9.1
  • the road towards EasyBuild 4.0
  • Q&A

Outlook to EasyBuild v3.9.1

The road to EasyBuild v4.0

  • ETA for EasyBuild 4.0 is (still) by summer 2019...

  • done: getting rid of strict requirement for setuptools dependency

  • WIP: renaming of 'dummy' toolchain to 'system' toolchain (by @boegel)

    • 'dummy' toolchain will be deprecated, using it will result in a big fat warning
    • under the hood 'dummy' will be translated to 'system'
    • dump easyconfigs (install dir, archive, etc.) will use 'system' rather than 'dummy'
    • CLI option for 'eb' to fix use of 'dummy', to easy transition?
    • support for toolchain = SYSTEM (to avoid need for toolchain = {'name': 'system', 'version': 'system'})
  • TODO: OpenMPI easyblock

    • logic to do a better job at default configuration of OpenMPI
    • conditional in case people already have site customizations (in easyconfig file or through hooks)
    • using the OpenMPI easyblock will be opt-in, so shouldn't be a huge problem?
  • Mikael: 2019b toolchains only in EasyBuild 4.0 or not?

    • related to request to join 'icc' & 'ifort' into a single 'iccfort' bundle...
  • minimal Python 3 version required is currently 3.5

    • may be able to lower that to 3.4 with a bit more effort
    • both Python 2.6 and 2.7 will also still be supported for EasyBuild 4.x...

Q&A

  • Davide: CUDA easyblock requires ldconfig (to install the stubs)?

  • Davide: testing through containers

    • being able to test on the cluster would help w.r.t. house electricity bill & providing more test reports
    • standardize on container setup
    • implement a bot that auto-tests PRs (failing test reports are not a huge issue)
    • Fotis: see buildtest by Shahzeb?
      • he was using Singularity 2.5(?) which was working fine
    • sharing (recipes for) container images
      • minimal vs fat
      • empty vs populated with toolchain/common deps (e.g. Python)
      • Fotis: orthogonal array testing (cfr. Markus)
      • starting point: minimal base container + standardizing mount points inside
    • set up a SIG for this?
      • Slack channel + dedicated mailing list(?) + extra slot for calls (in between EB conf calls?)
    • Davide & Kenneth will kickstart the effort & report back in (one of the) next conf call(s)
Clone this wiki locally