Skip to content

Conference call notes 20190206

Kenneth Hoste edited this page Feb 6, 2019 · 13 revisions

(back to Conference calls)

Notes on the 119th EasyBuild conference call, Wednesday Feb 6th 2019 (17:00 - 18:00 CET)

Attendees

Alphabetical list of attendees (XXX):

  • Damian Alvarez (JSC, Germany)
  • Fotis Georgatos (SDSC, Switzerland)
  • Victor Holanda (CSCS, Switzerland)
  • Kenneth Hoste (HPC-UGent, Belgium)
  • Adam Huffman (Big Data Institute, UK)
  • Alan O'Cais (JSC, Germany)
  • Mikael Öhman (Chalmers University of Technology, Sweden)
  • Bart Oldeman (ComputeCanada)
  • Davide Vanzo (Vanderbilt University, US)

Agenda

  • report on 4th EasyBuild User Meeting
  • follow-up on moving Python to GCCcore
  • standard (container-based) testing environment
  • Q&A

Report on 4th EasyBuild User Meeting

  • commonly requested features

    • support for uninstalling
    • Python 3 support
    • better logging/error reporting
      • Spack approach makes sense: use CMake regex patterns for "zooming in" on errors/warnings in logs
      • should also pick up config.log and include it in EasyBuild log?
  • integration with ReFrame

  • Spack talk

  • query about progress with .yeb easyconfigs (YAML syntax)

Follow-up on moving Python to GCCcore

Standard (container-based) testing environment

  • Singularity image(s)?
  • OS:
    • CentOS 7.x (cfr. EUM survey)
    • OpenHPC based?
    • more later?
  • EasyBuild installation
    • inside or outside container?
    • latest release vs current develop (there are use cases for both)
  • minimal vs fat installation
    • both are needed for good test "coverage" (cfr. problems with Boost system installation)
    • slightly less minimal environment needed to build GCCcore, can be stripped down later (no g++, etc.)
  • software/modules installation prefix outside of container
    • standard setup, e.g.:
      • /apps installation prefix which can be bind-mounted into container?
      • build dir in /tmp (or optionally /dev/shm)
  • clear MOTD to explain usage + point to dedicated docs

Other

Clone this wiki locally