Provisioning YAML Builder (PXE ➜ Live + SSH)

Build clean YAML structures locally in your browser. Enable JavaScript to use the interactive builder.

Configuration drafts for a provisioning workflow

This builder prepares Ubuntu autoinstall, cloud-init, Netplan, Ansible, iPXE and Terraform-variable artifacts from the settings in the form. Select a preview tab to inspect the file relevant to your next step. Each artifact has a different consumer and must be reviewed against that system’s requirements.

Prepare the settings and select the output

  1. Set the hostname, locale and time zone, then describe the network interfaces or bond your target system actually uses.
  2. Review the account and authentication settings. Replace example public keys; keep private keys and downloaded credentials within your approved administration process.
  3. Set kernel, initrd and seed URLs on infrastructure you control. Example URLs are placeholders: Root does not host a provisioning seed endpoint for this tool.
  4. Choose a tab and compare its generated preview with any manual override. The copy and download actions use the selected preview source, so inspect that source before exporting.

Platform and validation limits

The autoinstall output is designed around Ubuntu’s installer workflow. Choosing another distribution does not generate its native Kickstart, Preseed or Windows unattended-install file. Cloud-init, Netplan and Ansible artifacts are useful only where the target system supports the selected configuration.

The browser does not boot a server, contact the listed PXE endpoints or prove that the network can reach its gateway. Test syntax and deployment behavior using the consuming tool’s documentation and a disposable target. Keep console access available when testing a network or authentication change.

Use the Storage JSON Builder when you need a disk, partition or RAID draft. Its output has its own structure; review compatibility before combining configuration artifacts. For a managed business environment, see server administration and maintenance or network design and acceptance testing.

Your configuration stays in the browser

Configuration generation and key operations run locally after the assets load. Root does not receive the values entered into the builder. Save any required output before leaving or resetting the page, and protect downloaded files according to what they contain. Read the tool privacy details and usage terms.