Hardware requirements

The Management ISO VM and appliance nodes have been tested on these hypervisors:

This table records tested configurations only. It does not exclude other hypervisors or versions.

Both Management deployment options need the following resources:

For the Management ISO VM, use AMD64 virtual CPUs and one dedicated state disk. Keep the Management ISO attached and first in boot order for every boot. The state disk holds persistent host settings, Management data, credentials, images and logs. Allow space for bundle imports and operations and keep the disk access-controlled because it contains secrets.

For Docker or Docker Compose, reserve that capacity in the engine’s storage and mount a persistent volume at /var. Host and container-runtime overhead is additional. Choose the native image variant for the engine and check the minimum runtime versions.

Choose Standalone for one node or Three nodes for three nodes. Standalone has no node redundancy. Each appliance node needs UEFI firmware and three separate writable disks. Configure UEFI before the first boot and put the intended OS disk first in the boot order. Secure Boot may remain disabled.

Configure at least 16384 MiB for the minimum memory allocation. Disk capacities are decimal GB. Workload volume and retention can require more storage than these starting values. Management discovers eligible disks and requires one distinct disk for each role. It cannot use a single disk for several roles.

Minimum and recommended sizes use the same appliance service defaults. The recommended size provides more capacity for workload and recovery activity; it does not select a separate tuning profile or guarantee a particular transaction rate.

For VMware, the OVA’s supplied boot disk does not count as one of the three empty target disks. For Proxmox, retain the separate EFI disk required by the VM configuration. See the Proxmox and VMware deployment steps.

Reserve the IP addresses and DNS names for Management and the Appliance.