Closing the Gap Between Hardware and Cloud

# Summary

Infrastructure teams running VMware Cloud Foundation (VCF) have a mature software-defined stack above the hypervisor, but the physical side — bare-metal servers, firmware, BIOS, drivers, cabling, and accelerators — remains manual and brittle. MetalSoft and Broadcom are collaborating to automate the hardware lifecycle so physical infrastructure work aligns with VCF's operating model.

# The problem in plain terms

VCF makes compute, storage, and networking easy to provision at the software layer. Below that, adding a server to a VCF cluster typically requires manual steps: server discovery, BMC interrogation, BIOS and firmware configuration, driver and firmware baseline alignment, network and storage checks, GPU/NIC/DPU validation, ESXi install, compliance checks, and safe decommissioning.

Security and regulatory pressure adds urgency. The post cites a CrowdStrike figure for 2025 showing a large increase in AI-enabled attacks and points out that some enterprises have seven-day patching deadlines. The EU's DORA Articles 8 and 11 require automated firmware mechanisms, rapid severability, and recovery.

# Broadcom bring together

MetalSoft is described as an intent-based, API-first automation engine for physical infrastructure. It speaks Redfish, IPMI, BIOS controls, firmware catalogs, and switch provisioning, and maintains drivers and workflows for multiple vendors. MetalSoft publicly documents lifecycle management for Dell, HPE, Lenovo, and Supermicro, including firmware coordination and BMC/BIO S configuration.

Broadcom's involvement connects this physical orchestration to VCF so the boundary between physical and virtual infrastructure becomes less visible to operations teams. The partnership's stated goal for VCF customers is to make hardware easier to discover, prepare, provision, validate, and operate before and after joining the VCF estate.

# Concrete value areas called out

1. 1Heterogeneous hardware lifecycle management: multi-vendor orchestration that replaces fragile, vendor-specific runbooks and automations. MetalSoft maintains distinct drivers for different server models and variations in Redfish/BMC implementations.

1. 1Firmware and BIOS baseline handling: coordinated firmware catalogs and version alignment to reduce incompatibilities during ESXi upgrades and GPU-enabled node rollouts.

1. 1Inventory, validation, and compliance: automated hardware state collection, GPU/NIC/DPU validation, and drift detection to reduce human error and support rapid patch SLAs.

1. 1Safe decommissioning and lifecycle controls: policy-driven workflows for retiring or reassigning nodes with an auditable trail.

# Practical implications for VCF operators

• Expect fewer manual checklists for bringing new hosts into VCF, and less vendor-specific scripting.
• Faster, repeatable firmware alignment should reduce upgrade windows and unplanned outages tied to hardware mismatches.
• Improved auditability and automation can help meet short patch SLAs and regulatory clauses that require firmware management.

An Infrastructure Architect at a Fortune 500 financial services firm is quoted: "The question isn't whether to automate hardware lifecycle — it's whether you do it before or after a production incident forces the issue."

# What to watch next

Look for how the MetalSoft platform integrates with VCF workflows in practice across mixed-vendor fleets and whether automated firmware catalogs and baseline alignment materially reduce ESXi upgrade failures and downtime.