openskills.info
Course catalog
Course Preview

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

Bare-Metal Provisioning

Bare-metal provisioning turns an unconfigured physical server into a machine that can run an assigned workload. The process controls hardware directly. No hypervisor creates a virtual machine first.

That difference changes the job. A virtual-machine control plane already has programmable power, disks, consoles, and virtual networks. A physical server exposes those controls through firmware, a baseboard management controller, network-boot protocols, switches, and real storage devices. Provisioning coordinates all of them.

Use one mental model throughout this course:

desired server
    -> out-of-band control
    -> network bootstrap
    -> temporary in-band agent
    -> disk and host configuration
    -> local boot
    -> verified workload handoff

Each arrow crosses a boundary. Most failures come from locating the wrong boundary, not from a mysterious installer.

Provisioning is a lifecycle

Provisioning is broader than installing an operating system. It starts when you identify and enroll hardware. It continues through inspection, preparation, deployment, verification, use, deprovisioning, and cleaning.

A production system represents that lifecycle as explicit state. OpenStack Ironic, for example, distinguishes enrolled, manageable, available, deploying, active, cleaning, and failure states. The names vary across products. The principle does not: record what the controller believes, the transition it requested, and the evidence returned by the machine.

This state model makes retries safer. A controller can tell the difference between a machine ready for allocation and one waiting for a deployment agent. It can stop scheduling a node after a failed clean. It can also resume operator work from a known state instead of repeating every destructive action.

The two control paths

Continue the course

This section is part of the paid course.

See pricing to subscribe, or log in if you already have access.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources