Telcon: 2023 08 16

Wednesday August 16th, 9am PT (UTC -7:00)

Attendees

• Massimiliano Culpo (host)
• Jack Morrison
• Mark Krentel
• Raghu
• Dom Heinzeller
• Yang Liu

Agenda

• Raghu: Why intel-oneapi cannot be fetched from the default source mirror?

  • Massimiliano: I need to double check this specific case, but sometimes we have software that is not in our mirror because it cannot be redistributed. It might be the case that intel-oneapi is one of them.

• Raghu: Our use case imply that our users need to be able to reproduce bitwise any environment we built. Would you recommend sticking to a release or using develop?

  • Massimiliano: If the requirement is bitwise reproducibility, that cannot be achieved by just using develop. You have to stick to a specific version of Spack (either a tagged version or a specific commit) and provide that to your users. Also, Spack doesn't target bitwise reproducible builds, so there are aspects of the environment that you likely have to track yourself.

• Jack Morrison: Can someone review https://github.com/spack/spack/pull/39445 ? In general how can I highlight PRs for which I'd need a review?

  • Massimiliano: Mentioning them during the meeting is a good way. Another way would be to post them in the #pull_request channel on slack

• Yang Liu: What is the best practice, at a site, to provide Spack to users? Should we use a module file?

  • Massimiliano: There is no single best practice, but Spack supports different workflows / use cases. You might provide a module so that users can re-use a central installation of Spack (taking care of setting configuration properly in the module so that users don't step on each other toes), or just generate module files and advertize where you installed software centrally (so users can set the central installation as an upstream).

• Dom Heinzeller: I'd like to ping on some PRs

  • https://github.com/spack/spack/pull/38496
  • https://github.com/spack/spack/pull/39047