Skip to content

docs(changelog): add machine-a-tron to the v2.1 release notes #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
polarweasel merged 1 commit into from
Jul 31, 2026
Merged

docs(changelog): add machine-a-tron to the v2.1 release notes #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 22 additions & 1 deletion fern/changelog/2026-08-31.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
tags: ["next"]
tags: ["next", "machine-a-tron", "redfish"]
---

## NVIDIA Infra Controller v2.1 <Badge intent="launch">Next</Badge>
Expand All @@ -13,3 +13,24 @@ Placeholder text.
### Feature 2

Placeholder text.

### Validation & Testing

**machine-a-tron** is a bare-metal simulator that lets you run end-to-end NICo
provisioning flows — site-explorer, DHCP, PXE, ingestion, and state machines —
against mock Redfish BMC endpoints, without any physical servers or DPUs. It has
been validated at 4,500 simulated hosts × 2 DPUs (13,500 endpoints) in a single
unattended run.

It ships as the `nico-machine-a-tron` Helm subchart (enabled via
`nico-machine-a-tron.enabled=true`) with an end-to-end setup script at
`helm-prereqs/setup-machine-a-tron.sh` that handles namespace creation, credential
seeding, BMC proxy configuration, and verification. See the
[machine-a-tron deployment guide](../../docs/development/machine-a-tron-deployment.md)
for full build and deployment instructions.

<Note>
machine-a-tron is intended for simulation-only clusters and should not be used
alongside real hardware. It is not included in the `release/v2.0` branch —
v2.1 is the first release that ships it.
</Note>