Publishing worked; everything after it did not. Four things were wrong and each was silent in its own way. Versions were compared as text, so asking for "gromacs" with 2024.9 and 2024.10 published returned 2024.9. The whole meaning of an unversioned reference is "the newest one", and it was a wrong answer rather than a missing one - invisible until somebody noticed they had spent a week on last year's build. A recipe could hold one version while the catalogue could hold many, so an update either destroyed what it replaced or grew a parallel directory sharing nothing with the first. Recipes now carry a list, and the single-version form is read into the same shape, so nothing downstream knows which was written. An image was named by a mutable tag. Whoever repushes gromacs:2024.4 changed what every rebuilt cluster received, silently, and the record meant to freeze the cluster froze only its opinion of it. Two hashes are now recorded because they are checkable in different places: the manifest digest answers "has this moved" from the control plane, and the SIF hash is the only one a head can check with no network and no credential - which matters, because the head is where a wrong image does harm. Pulling by digest is deliberately not done: whether this Apptainer accepts an @sha256: reference is not established, and a provision failing at its last task over untested syntax would be worse than the problem. Module and binaries had been in the catalogue since it was written and were read by nothing - Module was referenced nowhere in the program. So a tenant was handed /opt/apps/gromacs.sif and left to work out Apptainer. They now become a wrapper per binary and an Lmod modulefile, and the answer is `module load gromacs`. Whether to pass --nv is decided on the node at run time: passing it without a driver fails outright, and omitting it where there is one leaves the job on the CPU saying nothing at all, which is the dangerous one. Four states replace `published:`. A withdrawn entry stays in the catalogue file, because dropping it would make it indistinguishable from one that never existed - and that difference is what an operator needs when a cluster is found still holding it. A pinned reference to one is refused with the recorded reason instead of "no application", which would send the user hunting for a typo in a correct name. The portal re-reads the catalogue when it changes, so publishing an application no longer needs a restart - the step that is invisible when forgotten. C20 ships the catalogue, which nothing did. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
26 lines
1.2 KiB
PL/PgSQL
26 lines
1.2 KiB
PL/PgSQL
-- How to run what a cluster was given.
|
|
--
|
|
-- A tenant was handed /opt/apps/gromacs.sif and nothing else: no wrapper, no
|
|
-- modulefile, no documented incantation. The catalogue had carried a module
|
|
-- name and a list of binaries since it was written, and neither was ever read
|
|
-- by anything - `Module` was referenced nowhere in the whole program. So the
|
|
-- platform shipped images and left the user to work out Apptainer.
|
|
--
|
|
-- These three travel with the cluster rather than being looked up, for the
|
|
-- same reason the image URI does: the head has no catalogue and must not
|
|
-- acquire one, or a cluster rebuilt after an edit to it would come back
|
|
-- running something else.
|
|
|
|
BEGIN;
|
|
|
|
ALTER TABLE cluster_app ADD COLUMN IF NOT EXISTS version text NOT NULL DEFAULT '';
|
|
ALTER TABLE cluster_app ADD COLUMN IF NOT EXISTS module text NOT NULL DEFAULT '';
|
|
ALTER TABLE cluster_app ADD COLUMN IF NOT EXISTS binaries text[] NOT NULL DEFAULT '{}';
|
|
|
|
COMMENT ON COLUMN cluster_app.version IS
|
|
'The version resolved from the catalogue. Names the modulefile: gromacs/2024.4.';
|
|
COMMENT ON COLUMN cluster_app.binaries IS
|
|
'What to put on PATH. One wrapper per entry, each running that binary inside the image.';
|
|
|
|
COMMIT;
|