Server heights from firmware and model; rack elevation at real size
Nobody types in how many units a server takes. Commissioning reads the SMBIOS chassis height; without one the model decides, from a table of heights checked against vendor documentation (Dell, HPE, Lenovo, xFusion, Fujitsu, Inspur/KAYTUS, GIGABYTE; Supermicro model numbers do not carry the height), and rack_units in config.json covers the rest and overrides both. Sleds of a multi-node chassis share its units. NetBox device types get the height (0 for sleds, which go into the rack without a position; Rollcall's own types are corrected). The rack elevation spans each server over its height, draws a chassis's sleds as one block, marks unknown heights and lists overlaps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
355401465c
commit
9b0b27fce6
12 files changed
+290
-16
No files matched your search
@@ -297,6 +297,17 @@ tag rules see `.Node.Building`, `.Node.Room`, `.Node.Rack`, `.Node.Unit`, so a
|
||||
rack can drive a tag (`{{ eq .Node.Rack "R12" }}`) or a Slurm `topology.conf`
|
||||
overlay.
|
||||
|
||||
**Server heights are not typed in.** `unit` is the lowest U a machine
|
||||
occupies; how many it takes comes from the firmware (SMBIOS type 3 "Height",
|
||||
read at commissioning), else from the model (a table of checked heights for
|
||||
Dell, HPE, Lenovo, xFusion, Fujitsu, Inspur/KAYTUS and GIGABYTE models, see
|
||||
`hwsize.go`), else from `rack_units` in `config.json` for models neither
|
||||
knows (`"rack_units": {"SYS-6029P-TRT": 2}`; it also overrides the others).
|
||||
Sleds of a multi-node chassis (Dell C-series, blades) share the chassis's
|
||||
units: the elevation draws them as one block, and NetBox gets a device type
|
||||
of height 0 placed in the rack without a position. The elevation spans each
|
||||
server over its height, marks unknown heights `?U` and warns about overlaps.
|
||||
|
||||
## Network and rack controllers
|
||||
|
||||
### Model
|
||||
|
||||
Reference in new issue
Block a user