From 95ae25dcd3f6c5ccf60ba0a6f76d2b049d393046 Mon Sep 17 00:00:00 2001 From: Shayan Namaghi Date: Wed, 29 Jul 2026 22:36:37 -0700 Subject: [PATCH] docs(changelog): add machine-a-tron to the v2.1 release notes machine-a-tron (#2764) landed in main after the release/v2.0 branch cut, so it ships first in v2.1. Move the entry from the v2.0 changelog to the new v2.1 file. Signed-off-by: Shayan Namaghi --- fern/changelog/2026-08-31.mdx | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/fern/changelog/2026-08-31.mdx b/fern/changelog/2026-08-31.mdx index 55fe4301ed..d00603d7d9 100644 --- a/fern/changelog/2026-08-31.mdx +++ b/fern/changelog/2026-08-31.mdx @@ -1,5 +1,5 @@ --- -tags: ["next"] +tags: ["next", "machine-a-tron", "redfish"] --- ## NVIDIA Infra Controller v2.1 Next @@ -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. + + +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. +