Skip to main content

turnup-check

Acceptance check for GPU halls: reads the intended build from NetBox or Nautobot, polls the hall over LLDP, Redfish and DCGM, and prints the diff. One command, seconds per rack, any vendor, Apache-2.0.

$ turnup-check --site hall-b --intent 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      4.1 s

report       hall-b-<YYYY-MM-DD>.json
share stats  --telemetry opt-in (racks, links)

Every finding comes with the fix a technician can act on. Exit code 0 means the hall matches intent, 1 means findings, 2 means the intent could not be read or no telemetry source answered. It writes one JSON report. Nothing else: no agent, no database, no account.

Install

pip install turnup-check            # Python 3.12+
pip install "turnup-check[snmp]"    # adds pysnmp for switches without eAPI/NVUE

Five minutes on a NetBox site

export NETBOX_URL=https://netbox.example NETBOX_TOKEN=...
export TURNUP_SWITCH_USER=admin TURNUP_SWITCH_PASS=...     # LLDP from the leaves
export TURNUP_BMC_USER=admin TURNUP_BMC_PASS=...           # Redfish from the nodes
turnup-check --site <slug> --intent netbox

--only lldp is the fastest first run: cabling only, switch credentials only. A device that refuses or does not answer is reported as unreachable, never fatal. Nautobot works the same way with --intent nautobot; so does a turnup.intent/v1 YAML file. What is read from NetBox, the device roles it expects, the management-endpoint custom fields and the firmware baseline are in docs/intent.md.

Try it without hardware

simhall is a virtual hall that serves the same NetBox, Redfish, eAPI/NVUE and DCGM protocols with fault injection. Its golden scenario reproduces the output above:

pip install simhall
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    # exits 1: one wrong_port
simhall act '{"kind":"seat_cable","label":"CBL-12-07-03","b_interface":"swp21"}'
turnup-check --site hall-b --intent http://127.0.0.1:8900/netbox    # exits 0: 288 / 288

Simulated runs are marked simulated: true in the report and never count anywhere.

What it finds

Finding Fix it prints
wrong_port: the NIC shows up on another switch port move cable one port up (or k ports down, or from leaf4/30 to leaf4/21)
missing_link: intended port empty, NIC seen nowhere seat cable CBL-12-07-03 at leaf4/21; check NIC when the BMC says the NIC port is down
link_degraded: right neighbor, port down or below intended speed check cable / transceivers
unexpected_link: a neighbor where intent has no cable trace and update intent
unreachable_node: Redfish down or HTTP error check reachability and credentials
firmware_off_baseline: a component differs from the baseline update bmc on node7 to 1.12.0
gpu_count_mismatch, gpu_unhealthy, nvlink_degraded, node_health_warning reseat, RMA packet, check NVLink, read the BMC log

A wrong_port is one finding, correlated across the NIC and both switch ports, never two. The exact rules, including what is a note rather than a finding, are in docs/findings.md.

How it works

Switches are read over Arista eAPI, NVIDIA NVUE or SNMP (LLDP-MIB); nodes over DMTF Redfish and the DCGM exporter. All devices are polled concurrently with a per-request deadline (--timeout, default 3 s), so a dead device never stalls the run; a clean hall costs about ten Redfish requests per node. docs/polling.md has the protocols, concurrency limits and the credentials file.

The report is turnup.report/v1 JSON with the summary, every finding with its evidence, and the sources that answered: docs/report.md. Telemetry is off unless you pass --telemetry; the payload is counts only, never names: docs/telemetry.md.

netbox_plugin/ holds netbox-turnup-check, a NetBox plugin that lists report files in a menu (netbox_plugin/README.md).

Status

v0.1.0. The NetBox and Nautobot adapters have run against the public demos (NetBox 4.7, Nautobot 3.2), not yet against a production GPU hall. The NVUE and SNMP paths follow the public docs and canned tables and have not been verified on a real switch. The full list is in docs/development.md, with how to develop, test and release.

Written from public specifications only: DMTF Redfish, IEEE 802.1AB LLDP and LLDP-MIB, NVIDIA DCGM-exporter metric names, NetBox and Nautobot REST API docs, Arista eAPI and NVIDIA NVUE public docs, the Prometheus exposition format. Example halls are synthetic.

License

Apache-2.0. See LICENSE.

Metadata

Release files for turnup-check 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 turnup-check 0.1.0
File Size Uploaded Provenance Actions
turnup_check-0.1.0.tar.gz 86.8 kB With provenance Details for turnup_check-0.1.0.tar.gz

Built distribution (wheel)

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

Total release size: 148.1 kB

Release files / turnup_check-0.1.0.tar.gz

Download URL turnup_check-0.1.0.tar.gz
Size 86.8 kB
Tags Source
SHA-256 checksum
How to use checksums
285ca28591331676f60e75f0c3f4925f8efc903649ff6d789f08e8a1dfb8c5c3
BLAKE2b-256 checksum
How to use checksums
d308dd468208ba8b7240768e2d03371280e3221f6ed3bdf2dd3ab9b863eea446
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 / turnup_check-0.1.0-py3-none-any.whl

Download URL turnup_check-0.1.0-py3-none-any.whl
Size 61.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ed0bc2afda2306e62d89a007092efa582049c55708c136b253027abd5f8d2a9c
BLAKE2b-256 checksum
How to use checksums
16ba85a87f2d773b1666fdc12b58a8f5a74a730f81b11d7d12cd8345d1ace8da
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 turnup-check 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 turnup_check-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