Files
ilker 6876e0c5bd Replace the Warewulf overlay UI with the HPC-on-Demand portal
hpc.example.org now serves the HPC-on-Demand portal, and the overlay UI is
gone - service, code, docs and the API it depended on.

The portal exposes phases 1 and 2 over HTTP: what the estate looks like,
which capabilities are schedulable and which are merely claimed, a dry-run
form, and the curated device map, plus a JSON API. It is entirely read-only
and provisions nothing.

It runs on the Caddy host bound to 127.0.0.1:9880, so the reverse proxy is the
only thing that can reach it - a smaller surface than the overlay UI had,
which listened on the management network. It refuses to bind off loopback
without a user file, for the same reason: the portal knows the shape and spare
capacity of the whole estate and holds read credentials for it. Discovery runs
on a two-minute timer rather than per request, since polling every backing
cloud on each page load would hammer their APIs and make the portal as slow as
its slowest site; pages report the inventory's age instead.

An unauthenticated /v1/ request now returns 401 rather than redirecting to the
login page. Sending a script an HTML form instead of a status code it can act
on is the kind of thing that wastes an afternoon.

Removing the overlay UI also disabled the Warewulf REST API on head01, which
had been enabled solely to serve it. Leaving root-equivalent access switched
on with no consumer would be a liability, so warewulf.conf and auth.conf were
restored from the pre-feature backups and the firewall rule dropped. The
cluster was re-verified afterwards: four nodes idle, an eight-rank MPI job
completing.

Also adds the phase 3 Terraform module for one tenant - isolated bridge, head
node and diskless compute nodes with deterministic MACs, since Warewulf
matches nodes by MAC and a regenerated one would orphan the registration. Not
yet applied against a real site.
2026-09-01 12:24:54 +02:00

32 lines
1.3 KiB
HTML

<!doctype html><html lang="en"><head><title>Device map · HPC on Demand</title>{{template "head" .}}</head>
<body>{{template "nav" .}}
<main>
<h1>Curated device map</h1>
<p class="deck">PCI class codes are enough for GPUs and NVMe, but cannot identify InfiniBand.
Every row here records something a class code cannot say.</p>
<div class="note">
<p>A ConnectX-4 Lx reports class <code>0x0200</code> — Ethernet — because that variant is
Ethernet-only. A ConnectX-6 reports <code>0x0207</code> in IB mode and <code>0x0200</code> in
Ethernet mode. Class-based detection therefore produces both false negatives and false
positives, so a fabric capability is never schedulable until a node agent confirms the link
is actually up.</p>
</div>
<div class="card"><div class="card-b">
<table>
<thead><tr><th>Vendor</th><th>Device</th><th>Capability</th><th>Why this row exists</th></tr></thead>
<tbody>
{{range .CapMap}}
<tr>
<td><code>{{.Vendor}}</code></td>
<td><code>{{.Device}}</code></td>
<td><span class="pill muted">{{.Capability}}</span></td>
<td class="age">{{.Note}}</td>
</tr>
{{end}}
</tbody>
</table>
</div></div>
</main></body></html>