A container registry stores bytes. Nothing in an OCI manifest says that a particular GROMACS build needs a GPU, how large it is, what module name it exposes, or whether anyone signed it. That is what this catalogue carries, and it is why a registry alone was not enough. The effect is that a request can name what someone actually wants. A request for "gromacs" states no hardware at all; the catalogue resolves it to the newest published build, which declares a GPU requirement, and placement is handed that requirement as if it had been written down. Verified through the endpoint, not only in unit tests: posting a request whose only content is `apps: [gromacs]` comes back with the resolved image and a derived GPU constraint. Someone who wants the software should not have to know the hardware it implies, and if they forget, they should not be placed on a site that cannot run it. Expansion happens before placement, not inside it. Placement matches constraints against hardware; which build of which application wants a GPU is catalogue knowledge, and mixing the two would mean placement's tests had to carry an application list to say anything about scheduling. It also leaves the caller's request untouched, so examining a request twice does not grow its constraints. A YAML file rather than a service, deliberately, for the same reason sites.yaml is one: it is read, not written, and only the platform team publishes to it. It becomes a service the day someone else needs to write to it. A missing file is an empty catalogue rather than an error - publishing no applications is a legitimate configuration and the control plane still has to start - but an entry without an image is rejected at load, because the alternative is finding out when a tenant tries to pull it. An unknown application is an error, not a warning. Provisioning a fourteen- day cluster and only then discovering that the software someone came for was never published is the wrong order to find out. Version resolution prefers the newest, so "openfoam" means the latest published OpenFOAM rather than whichever happens to be first in the file. Not yet built: the provisioning half that pulls the resolved images onto a tenant's /opt. size_gb is in the schema for the decision it will drive - whether an image is small enough to pull while provisioning, or large enough that it belongs in the template or in a fetch after the cluster is already usable, rather than back on the critical path.
22 lines
457 B
YAML
22 lines
457 B
YAML
# A request that names applications instead of hardware.
|
|
#
|
|
# Nothing here asks for a GPU. The catalogue knows that this build of GROMACS
|
|
# needs one, so placement is given that requirement anyway - which is the
|
|
# point: the person who wants the software should not have to also know the
|
|
# hardware it implies.
|
|
name: md-study
|
|
lease: 7d
|
|
|
|
head:
|
|
cores: 4
|
|
memory_gb: 8
|
|
disk_gb: 120
|
|
|
|
compute:
|
|
count: 4
|
|
cores: 8
|
|
memory_gb: 32
|
|
|
|
stack:
|
|
apps: [gromacs]
|