Four things stood between a spack.yaml recipe and an image, and all four were invisible because nothing had ever run this path: every Spack recipe in the catalogue was still draft. The default builder image was spack/rockylinux9:v0.23.1, a tag that has never existed - Spack's images are tagged by release and Spack went to 1.x. Pinned to 1.2.2 rather than :latest, because the concretizer decides the whole catalogue's ABI and should not change under us between two applications. Spack was assumed to be on PATH. `spack env activate` changes the calling shell, so it is a function that setup-env.sh defines; running the binary prints what it would have set and changes nothing. config: install_tree took a bare path, which Spack 1.x rejects. And the MPI line could not concretize at all: +pmi and +legacylaunchers exist only up to OpenMPI 4, so asking for them with @5.0.6 collapsed the spec to 4.1.8 and then refused it. OpenMPI 5 is launched by srun through PMIx, and ~internal-pmix is what makes it use the external pmix@4.2.9 the recipes pin - without it OpenMPI bundles its own and the pin means nothing. The build cache was a dead wire at both ends. The template read from $SPACK_MIRROR and build-push.sh never passed it, and nothing ever pushed, so it could only have been empty. It is now passed by default, pointing at the same registry the images go to, and the install autopushes - during, not after, so a build that fails on its last package still leaves the half hour of OpenMPI before it. Reading needs no credential, because the registry is public by design; writing does, and it arrives as a mounted secret rather than a build argument. Arguments are recorded in the image metadata, and these images are published - a token passed that way would ship inside every application in the catalogue. osu-micro-benchmarks is the first entry that claims to run across nodes. Everything else says single-node, so the path that carries ranks between two machines had never been exercised by anything the catalogue offers. Its binaries are declared by absolute path because that is where OSU puts them: under libexec, which the view carries and nothing puts on PATH, so a bare name would be a promise the image does not keep. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
38 lines
1.2 KiB
YAML
38 lines
1.2 KiB
YAML
# Quantum ESPRESSO. ScaLAPACK is not optional here in practice: without it
|
|
# the k-point parallelisation is the only one available, and a run that
|
|
# would have used 128 ranks uses 8 and looks like the cluster is slow.
|
|
spack:
|
|
specs:
|
|
- quantum-espresso@7.3.1 +mpi +scalapack +openmp ~qmcpack
|
|
# +pmi and +legacylaunchers exist only up to OpenMPI 4
|
|
# (`when @1.5.5:4 schedulers=slurm`), so this line pinned to 5.0.6
|
|
# could not concretize at all - it collapsed to 4.1.8 and then
|
|
# refused. OpenMPI 5 is launched by srun through PMIx instead, and
|
|
# ~internal-pmix is what makes it use the external one pinned below
|
|
# rather than bundling its own.
|
|
- openmpi@5.0.6 ~internal-pmix schedulers=slurm fabrics=ofi,ucx
|
|
|
|
packages:
|
|
all:
|
|
providers:
|
|
mpi: [openmpi]
|
|
blas: [openblas]
|
|
lapack: [openblas]
|
|
scalapack: [netlib-scalapack]
|
|
target: [x86_64_v3]
|
|
pmix:
|
|
require: ["@4.2.9"]
|
|
openblas:
|
|
require: ["threads=openmp"]
|
|
|
|
concretizer:
|
|
unify: true
|
|
reuse: true
|
|
|
|
config:
|
|
# Spack 1.x wants an object here; the bare path that 0.23 took is
|
|
# rejected with "'/opt/software' is not of type 'object'".
|
|
install_tree:
|
|
root: /opt/software
|
|
view: /opt/view
|