11. Digital Rebar Provision Workflows¶
PXE Provisioning requires hand-offs between multiple services and the nodes. Generally, these flows start with network discovery (DHCP) providing a “next boot” instruction to the server’s pre-execution environment (PXE) that can download a very limited operating system using a very simple file transfer protocol (TFTP). That next operating system can then take more complex actions including using HTTP to download further files.
Digital Rebar Provision does not provide out-of-band management or orchestration in the Open Source version. See the RackN based advanced plugins for power management capabilities.
In the flow graphics, green steps indicate user actions.
11.1. Basic Discovery¶
The basic discovery flow uses the specialized Discovery and Sledgehammer Boot Environments (BootEnvs). These BootEnvs work with the default next boot to self-register machines with Digital Rebar Provision using the Machines API.
This recommended process allows operators to start with minimal information about the environment so they can Provision O/S on Discovered Systems. Without discovery, operators must create machines in advance following the Provision O/S on Known Systems process.
11.2. Provision O/S on Discovered Systems¶
Once systems have been discovered using Basic Discovery, their machine BootEnv can be set to an O/S installation image. The recommended BootEnvs for these images includes an automatic machines API call that sets the machine to boot to local disk (BootEnv = local).
11.3. Provision O/S on Known Systems¶
|note:||This workflow requires users to know their machine information in advance.|
This is the typical workflow for Cobbler users in which machine definitions are determined in advance using spread sheets, stone tablets, Ouija boards or other 1990s data center inventory management techniques.
Two advantages to this approach is that it skips the discovery boot process; consequently, it is faster and can be run without DHCP.