VM Provisioning

Updated Aug 14, 2026, 5:52 PM UTCSource: docs/data/factory-stats.json + live Zot registryRaw dataset

Fleet Overview

Hypervisor Nodes

KubeVirt-capable cluster members

Cluster RAM

125 GiB

Total allocatable memory

Cluster CPU

64 Threads

Total allocatable threads

ContainerDisk Builds (7d)

421

1567 builds all-time

Hypervisor Capacity

Installed RAM and CPU threads per KubeVirt-capable node. Actual VM packing is constrained by k8s scheduler requests and the qa-vm-fleet template semaphore.

Cluster aggregate capacity derived from docs/data/factory-stats.json factory.cluster.nodes.

Guest Filesystems

Distribution of root filesystems across the published containerDisk catalog. Values reflect the filesystem selected by bootc install-to-disk or the upstream image, not the host format.

Filesystem mapping sourced from argo/workflow-templates/build-containerdisk.yaml and provision-flatcar-vm.yaml.

ContainerDisk Inventory

Published VM boot images in the local Zot registry. Sizes are OCI layer sizes; the raw disk unpacked inside the virt-launcher pod is larger.

Image	Tag	Status	Guest FS	Size	Digest	Created
Bluefin	testing	available	btrfs	N/A	N/A	N/A
Bluefin	lts-testing	available	xfs	N/A	N/A	N/A
Bluefin	stable	available	btrfs	N/A	N/A	N/A
Bluefin	lts-stable	available	xfs	N/A	N/A	N/A
Flatcar	latest	available	ext4	N/A	N/A	N/A

Hypervisor Nodes

KubeVirt-capable cluster nodes that can schedule test VM workloads.

Name	Role	Status	OS	Kernel	RAM	CPU Threads	Memory Use	CPU Use
exo-0	worker	ready	Fedora CoreOS 44.20260707.3.1	7.1.3-200.fc44.x86_64	62 GiB	32	29.4%	1.8%
ghost	control-plane	ready	Bluefin (Version: testing-44.20260708.3)	7.1.3-200.fc44.x86_64	63 GiB	32	16.5%	3.7%

Provisioning Architecture

Test VMs boot from OCI containerDisk images stored in the local Zot registry (192.168.1.102:30500). Each pipeline run pulls the disk image and launches a fresh KubeVirt VM. The VM is torn down on exit.

ContainerDisk VMs schedule on any KubeVirt-capable node; PVC-backed lanes co-schedule on the PVC node.
Bluefin non-LTS uses btrfs; Bluefin LTS uses xfs; Flatcar uses ext4.
SSH keys are injected at runtime via KubeVirt accessCredentials; no key material is baked into images.

Provenance: node capacity and containerDisk build counts from docs/data/factory-stats.json; disk catalog live-polled from ghost Zot (fallback marks unavailable).Raw dataset