/admin/capacity, administrators only. They were always read together: one page says
how busy the hardware is and the other says which hardware there is.
The old
/utilization and /fleets links land here. ?tab=fleets/<fleet-id> opens one Fleet’s
machines, which fill the page on their own.
The Utilization tab
Unschedulable is not busy. A card lands there when health checks found pending ECC retirements or
uncorrected errors, or when a process outside the platform is holding it.
The Fleets tab
A Fleet is a registered, named set of machines that one backend manages, and it is the thing a job or a deployment is placed onto.
Those four inventory statuses are never rounded into each other. An unknown reading proves
nothing, so it refuses no job and admits none by fallback, and an unreported card count reads as
null rather than 0. A backend that could not be reached is not a cluster with nothing in it.
Discovery says what exists. It never says what is free.
What you can do
Only a
node Fleet registers machines here. Kubernetes owns its nodes, Slurm owns its nodes, and
local owns exactly the host the console runs on — so a Join Token, a node credential and a
heartbeat mean something on node and nothing anywhere else. Asking for one on a kuberay Fleet
is refused rather than producing a record nothing can honour.
External inventory is read-only. The platform does not cordon a Kubernetes node or drain a Slurm
partition: a control plane that mutates somebody else’s scheduler needs an argument this one has
not made.