Skip to main content

simhall

A virtual GPU hall for testing bring-up tooling without hardware. One ground-truth model serves the devices a bring-up tool talks to, with fault injection and technician actions: Redfish BMCs, LLDP tables on Arista (eAPI) and NVIDIA (NVUE) leaves, DCGM exporters, and a minimal NetBox API. Apache-2.0.

pip install simhall turnup-check
simhall serve --golden hall-b &                                      # 127.0.0.1:8900, any token
turnup-check --site hall-b --intent http://127.0.0.1:8900/netbox
reading intent      288 links · 18 nodes · 2 leaves
polling             lldp · redfish · dcgm
✓ 287 / 288 links match intent
✓ 18 / 18 nodes reachable, firmware baseline ok
✗ mismatch   node7 mlx5_3 → leaf4/22
             expected leaf4/21
fix          move cable one port up
elapsed      0.4 s

A technician seats the cable, and the same command exits 0 with 288 / 288:

simhall act '{"kind":"seat_cable","label":"CBL-12-07-03","b_interface":"swp21"}'

Everything here is synthetic: no real hostnames, IPs, serial numbers or topologies. The intent it emits carries simulated: true, so a simulated run never counts as a real one.

Why

Bring-up tooling is tested on the hardware it is meant to verify, which is the hardware nobody can spare. simhall gives a tool like turnup-check a hall that behaves like the real protocols at every layer, where any fault can be injected, observed through every view at once, and cleared again byte for byte. The test suite of turnup-check runs thousands of random halls and fault sets against it in-process.

Install

pip install simhall                                     # Python 3.12+
pip install git+https://github.com/turnup-dev/simhall   # or straight from this repository

From a checkout: pip install -e '.[dev]', then simhall --help. Dependencies: fastapi, uvicorn, pydantic v2, httpx, pyyaml, click; pynetbox only for simhall seed-netbox (.[netbox]).

Faults and what a tool should see

Fault Observable effect Expected turnup-check finding
wrong_port(cable, to_device, to_interface) neighbor appears on the target port, intended port down; node Redfish port shows the target wrong_port
missing_link(cable) intended port down, no neighbor anywhere; node port NoLink missing_link
swap_pair(a, b) the two cables' leaf ports are exchanged 2 x wrong_port
link_degraded(cable, 200 | "down") speed 200G on both ends, or link down with an aging LLDP entry link_degraded
unreachable_node(node, timeout | http_500 | refused) Redfish and/or DCGM answer per mode; links stay up unreachable_node
firmware_off_baseline(node, component, version) the inventory member's version changes firmware_off_baseline
gpu_unhealthy, gpu_missing, nvlink_degraded, node_health_warning DCGM metrics and Redfish health change accordingly the matching finding
pdu_outlet_off(node) BMC and exporter refused, host off, every link down unreachable_node + missing_link per port
coolant_leak, partial_redfish, lldp_port_id_mac leak detectors Critical; FirmwareInventory 404; port ids as MACs none, by design

Actions (seat_cable, unseat_cable, power_on, power_off, replace_node, update_firmware, scan_qr) change the hall the way a technician would and retire the faults they physically resolve. Faults are applied on top of the base state and clearing one restores the views exactly, in any order. The complete tables and the rules are in docs/faults.md.

Python API

from simhall import HallSpec, Hall, Fault, Action

hall = Hall.generate(HallSpec(site="hall-b", racks=1, nodes_per_rack=18, ports_per_node=16,
                              leaves_per_rack=2, switch_vendor="nvidia", seed=1))
hall.inject(Fault(kind="wrong_port", cable="CBL-12-07-03", to_device="leaf4", to_interface="swp22"))
hall.lldp_table("leaf4")        # what the leaf would say
hall.redfish_tree("node7")      # what the BMC would say
hall.act(Action(kind="seat_cable", label="CBL-12-07-03", b_interface="swp21"))

create_app(hall) serves that very object over HTTP, so in-process actions are visible to a tool polling it. The model, the cabling rule and how state is derived: docs/model.md.

Documentation

License

Apache-2.0. See LICENSE.

Metadata

Release files for simhall 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for simhall 0.1.0
File Size Uploaded Provenance Actions
simhall-0.1.0.tar.gz 84.1 kB With provenance Details for simhall-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for simhall 0.1.0
File Interpreter ABI Platform Actions
simhall-0.1.0-py3-none-any.whl Python 3 none any Details for simhall-0.1.0-py3-none-any.whl

Total release size: 149.8 kB

Release files / simhall-0.1.0.tar.gz

Download URL simhall-0.1.0.tar.gz
Size 84.1 kB
Tags Source
SHA-256 checksum
How to use checksums
97730fe513d0e4c19be29d21a797b6ffc3401c944ce28707d0a8a4c602308699
BLAKE2b-256 checksum
How to use checksums
a116f70d4542f724f677efd9fa9686b9c6816832786a2a3d5d9e02fb9c0c4244
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.

Transparency log

Release files / simhall-0.1.0-py3-none-any.whl

Download URL simhall-0.1.0-py3-none-any.whl
Size 65.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
77e8ee8026bb6dace8dc6e342acdbc3f77a58c2da51ca10a97f01a77ae0f8ed4
BLAKE2b-256 checksum
How to use checksums
f970d18481ff272ae110010579a07fda408d27018c3966df430041e53d1850fa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.

Transparency log

Security for simhall 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for simhall-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 25, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page