Bare-Metal Provisioning

Bare-metal provisioning is the process of taking an empty physical server from power-on to a running operating system without manual intervention. It covers network booting, firmware configuration, OS installation, and the automation tooling that makes this repeatable at scale.

itInfrastructure and operations

Don't Panic — Bare-Metal Provisioning

Bare-metal provisioning is how an unconfigured physical server becomes a verified machine for a workload. It is not an operating-system installer with better posture. The installer is only one passenger in a relay involving power, firmware, networks, storage, and a certain amount of hardware that has not read the same manual as the rest of it.

The baseboard management controller, or BMC, starts the relay. It can power the server, select a one-time boot source, and show a remote console even when no host operating system exists. Firmware then follows a network bootstrap path: DHCP provides the address and boot information, a network bootstrap program begins, and a small service system reaches the machine. That temporary system is the deploy agent. It sees the disks and devices that the controller cannot touch from afar.

The surprising bit is that PXE is not one event. A DHCP lease says that DHCP worked. It does not say that the boot program suits the firmware, that the ramdisk started, or that the agent can call back. Each step is its own boundary, which is mildly inconvenient until it saves you from treating every failed deployment as an occult property of servers.

Once the agent is running, it can inspect hardware, select storage, erase old data, write an image, and arrange local boot. A whole-disk image brings its partition layout and boot loader. A partition image asks the provisioner to create more of that arrangement. Server-specific data, such as a hostname and initial keys, belongs beside a reusable base image rather than baked into every copy.

Provisioning is complete only after local boot, expected identity, network reachability, and health checks agree. Then configuration management or an application bootstrap can take over. The relay also runs in reverse: cleaning prepares the machine for reuse. Removing disk metadata is fast; it does not prove that old data is gone, and disk cleaning does not validate firmware. Physical machines enjoy having several separate ways to retain a past life.

Read the introduction for the full architecture and trust boundaries. Use the slides when you need the relay and lifecycle in one view. Keep the cheatsheet nearby when the last confirmed event tells you which boundary to inspect next. The reference tab leads into the standards and Ironic documentation that define the protocols and state transitions in detail.

Don't Panic — Bare-Metal Provisioning

Relevant careers