Deploy from the VM Catalog¶
The 🗂 VM Catalog is a curated set of one-click VM blueprints for internal infra teams — each blueprint fixes a template, size, network, and storage backend so deploying is either a single click or a CSV of many rows for a batch. It's a different feature from the Catalog tab (Pull an LXD Image, Install a TurnKey Appliance), which is about LXD container images, not VM blueprints.
Deploy a single VM¶
- 🗂 VM Catalog.
- Pick a blueprint card and click it — you're prompted for a VM name, then it deploys with the blueprint's fixed template, vCPU/RAM/disk size, OS type, network, and storage backend (local/ZFS/Ceph/NFS).
Bulk deploy from a CSV¶
- 🗂 VM Catalog → ⬇ CSV Template to download a starter CSV.
- Fill in rows with columns:
- vm_name (required)
- blueprint (required) — must match a blueprint's name exactly.
- target_host (optional) — a specific hostname,
auto:<cluster>to place anywhere in that cluster, or leave blank for fleet-wide DRS-lite automatic placement. - network_name (optional) — overrides the blueprint's default network.
- ⬆ Bulk Deploy (CSV), pick the file.
- Results appear in the Bulk Deploy Results table — one row per CSV row, with status and the assigned host or error detail.
Limits: up to 200 rows per batch; the CSV must be UTF-8.
Creating a blueprint (admin)¶
+ New Blueprint (admin-only) — set name, description, icon, source template, vCPUs, memory, disk size, OS type, network, and storage backend (with the matching pool/datastore name for ZFS/Ceph/NFS). Set Status to hidden to keep a blueprint out of the deploy grid without deleting it (existing CSV rows referencing it will still fail with a clear error once hidden).
See also¶
- Create a Golden Image Template — blueprints deploy from templates; create one first if you don't have a suitable source.
- Create a Virtual Machine — the manual, one-off equivalent with full control over every setting.