The catalogue assumed oras:// for any image it had no record of, which put an OCI image in it under an ORAS reference; every head that pulled it failed with "invalid layer mediatype". The scheme is now read from the registry's manifest - a SIF layer is oras://, an OCI layer docker:// - and an image whose shape cannot be read is left out and named, rather than guessed. build-push.sh checks before building that it has somewhere to write the catalogue, and after pushing that what it pushed is in it under the reference it was pushed as. osu-micro-benchmarks is built, pushed and pulled back, and offered. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
28 lines
1.3 KiB
YAML
28 lines
1.3 KiB
YAML
name: osu-micro-benchmarks
|
|
version: "7.5.2"
|
|
description: Point-to-point and collective MPI benchmarks. What you run to find out whether the fabric works, and how fast, before blaming an application.
|
|
homepage: https://mvapich.cse.ohio-state.edu/benchmarks/
|
|
module: osu-micro-benchmarks
|
|
# Absolute paths, because that is where they are. OSU installs under
|
|
# libexec rather than bin - the view carries it, but nothing puts it on
|
|
# PATH - so a bare name would be a promise the image does not keep, and
|
|
# the check that asks the image for its binaries would be right to refuse.
|
|
binaries:
|
|
- /opt/view/libexec/osu-micro-benchmarks/mpi/pt2pt/osu_latency
|
|
- /opt/view/libexec/osu-micro-benchmarks/mpi/pt2pt/osu_bw
|
|
- /opt/view/libexec/osu-micro-benchmarks/mpi/collective/osu_alltoall
|
|
# The first entry in this catalogue that claims to run across nodes, and
|
|
# the reason it exists. Everything else says single-node, so the path that
|
|
# carries ranks between two machines - srun, PMIx, the container's own MPI -
|
|
# had never been exercised by anything the catalogue offers.
|
|
mpi: multi-node
|
|
requires: []
|
|
license: BSD-3-Clause
|
|
signed: false
|
|
|
|
# Built, pushed, and pulled back from the registry by build-push.sh, which
|
|
# is what this word is a promise about: the head can pull it. That it runs
|
|
# across two nodes is the next thing to prove, and the reason this entry
|
|
# exists.
|
|
status: available
|