feat: Add support for Supermicro GB300 NVL (SMC "GB NVL") host platform

[shevchenko-evgeny]

Is this a new feature, an enhancement, or a change to existing functionality?

New Feature

How would you describe the priority of this feature request

High

Please provide a clear description of problem this feature solves

NICo cannot fully explore or provision Supermicro GB300 NVL trays (Redfish ServiceRoot Vendor=Supermicro, Product="GB NVL"; System Manufacturer=Supermicro, Model="GB NVL") carrying a BlueField‑3 DPU.
Hardware

• Host: Supermicro GB300 NVL tray. BMC is OpenBMC‑based; Redfish schema is close to the NVIDIA GB200/GBx00 family but uses the Supermicro OEM namespace.
• DPU: NVIDIA BlueField‑3, on PCIe slot 6.

Feature Description

Add native support in NICo for provisioning and managing Supermicro GB300 NVL host trays (Supermicro host BMC + BlueField‑3 DPU).
Today NICo does not recognize this platform so the host cannot be onboarded or provisioned. This feature would teach NICo to identify the Supermicro GB300 NVL as a first‑class platform and handle its BMC's specific behaviors (Redfish vendor quirks, BIOS/boot setup, and DPU reprovisioning) so these servers can be brought under NICo management the same way as the other supported GB200/GB300 variants.

Describe your ideal solution

A Supermicro GB300 NVL host is auto‑detected, explored without errors, and provisioned end‑to‑end - BIOS setup, boot, and DPU reprovisioning - with no manual workarounds. Firmware update, health checks, and telemetry collection are all fully supported.

Describe any alternatives you have considered

No response

Additional context

No response

Code of Conduct

• I agree to follow NVIDIA Infra Controller's Code of Conduct
• I have searched the open feature requests and have found no duplicates for this feature request

[deepak-poornachandra]

@shevchenko-evgeny - Is there a timeline on this ?

[shevchenko-evgeny]

@deepak-poornachandra We have rolled out the MVP version in the lab: machine onboarding and instance provisioning are working well, although some manual interventions are still required due to missing BMC functionality.
We will submit all our changes early next week.

[martinraumann]

Current upstream status:

Merged so far:

• feat: minimal SMC GB300 support libredfish#111 - minimal OpenBMC-based Supermicro GB300 support.
• feat: minimal SMC GB300 support #4121 - minimal NICo-side SMC GB300 support; bumps libredfish and adds bmc-explorer/bmc-mock
  handling.
• backport: minimal SMC GB300 support (#4121) to release/v2.1 #4645 - backport of feat: minimal SMC GB300 support #4121 plus GB300 boot artifact / scout boot-NIC fixes to release/v2.1.
• fix: distinguish Supermicro and DGX GB300 BIOS behavior libredfish#129 - separates Supermicro GB300 BIOS behavior from DGX GB300 behavior.

Open / follow-up:

• fix(bmc-explorer): pick the manager whose ManagerForServers links the explored system #5512 - fixes bmc-explorer manager/system pairing on multi-system or multi-manager BMCs.

Known remaining firmware/BMC gaps:

• HTTP boot can be enabled manually in BIOS, but the BMC Redfish surface does not appear to expose the BIOS attribute
  needed to enable it programmatically.
• BootOrder PATCH appears to reject removing some existing entries, such as the UEFI shell entry, even when reordering
  otherwise works.