Skip to content

Conference call notes 20191211

Jump to bottom
Kenneth Hoste edited this page Dec 11, 2019 · 4 revisions

(back to Conference calls)

Notes on the 138th EasyBuild conference call, Wednesday Dec 11th 2019 (17:00 - 18:00 CET)

Attendees

Alphabetical list of attendees (8):

  • Fotis Georgatos (SDSC, Switzerland)
  • Victor Holanda Rusu (CSCS, Switzerland)
  • Kenneth Hoste (HPC-UGent, Belgium)
  • Alan O'Cais (JSC, Germany)
  • Mikael Öhman (Chalmers University of Technology, Sweden)
  • Bart Oldeman (ComputeCanada)
  • Åke Sandgren (Umeå University, Sweden)
  • Davide Vanzo (UT Southwestern)

Agenda

  • update on recent developments
  • installing CUDA software: picking list of CUDA compute capabilities
  • Q&A

Update on recent developments

Installing CUDA software

  • see CuCLARK PR: https://github.com/easybuilders/easybuild-easyconfigs/pull/9482
  • do we need support in framework to deal with this properly?
    • we should add a dedicated configuration to specify the CUDA compute capabilities
    • other relevant easyblocks/easyconfigs that could use this include PyTorch, RELION, VMD, Amber?
  • current CUDA support in toolchains already has a way to specify a list of CUDA compute capabitilities via toolchainopts
    • but that's not a general setting, can only be specified in easyconfigs
    • only results in setting $CUDA_CXXFLAGS & co (not $NVCCFLAGS)
  • related: we're no longer specifying CUDA compute capabilities for TensorFlow, shouldn't we?
    • looks like we stopped doing so when we started using the Bundle or PythonBundle easyblock in TensorFlow easyconfigs
    • so the question is what TensorFlow does by default...

Q&A

  • Alan: container support is still installing vsc-base as a requirement for EasyBuild
    • see opened issue
  • Victor: modules generated by EasyBuild do not ensure that FFTW libraries are linked
    • see buildenv module
      • set $CFLAGS & co
    • Cray compiler wrappers automatically link to FFTW libraries when cray-fftw module
  • Åke: currently only buildenv/default in HMNS, should also have variants for foss vs intel, etc.
    • actual reason is escaping Åke right now
    • could be to discriminate between buildenv for subtoolchains
    • Alan: also set $CMAKE_* flags?
    • should be done for all modules we generate, not just buildenv?
    • only picked up if NO_DEFAULT_PATHS is not set in Find* CMake functions
      • this is often used, often need to patch this out
  • Alan: progress on talks from EUM?
    • opening talk with EasyBuild update
    • talks proposals by John Dey (easy_update), buildtest, ReFrame, Sarus (container runtime by CSCS)...
    • tutorial on contributing back (more extensive than last year)
    • invite BEAR people to talk about EasyBuild on POWER?
    • (remote) talk with Spack update by Todd or Massimiliano?
    • Åke: maybe a talk on doing production builds in a "clean room" environment using Singularity containers
    • update on OpenHPC (2.0)?
  • Victor: support in EasyBuild to submit installations to Kubernetes?
    • Fotis: does GC3Pie support this? (ask Riccardo Murri...)
  • Åke: parallel setting should be using N times # available cores to make sure resources are used well...
Clone this wiki locally