Host Requirements & Name Resolution
Plan system resources for the controller, compute workers, and storage workers, then verify stable host name resolution before enrollment. Each worker must resolve and reach the controller; the controller must resolve its workers.
System requirements
STRATUM runs as an application on your existing Linux host. These are initial STRATUM planning estimates, not fixed minimum hardware specifications; add the operating system, container runtime, logging, storage capacity, and actual workloads when sizing the host.
| Host role | STRATUM planning estimate | I/O and workload considerations |
|---|---|---|
| Controller | 10–20 MB RAM per worker Approximately 1 vCPU per 100 workers | Allow additional base CPU/RAM for controller services and for the number of concurrent tasks, logs, and operations. |
| Compute worker | STRATUM's own resource needs are comparatively low. Size primarily for the VMs and containers you plan to run. | For VM snapshots, provision good, fast disk I/O, adequate free space, and headroom for snapshot changes. |
| Storage worker | 10 MB RAM per worker Approximately 1 vCPU per 50 workers | Good, fast network connectivity and disk I/O are essential for VM images, disk access, placement, and snapshot activity. |
These estimates are per managed worker and exclude guest VM memory and disk capacity. Validate against your workload mix: concurrent VM starts, storage demand, network throughput, high availability, and accelerator usage can change the required capacity.
Where dedicated physical links are available, see Multi-Homed Workers to separate management and VM uplink traffic.
Supported CPU architectures
Supported CPU architectures: STRATUM Continuum supports mixed x86-64, Arm64/AArch64 and s390x nodes, including s390x enterprise deployments. Guests must execute on matching-architecture workers; cross-architecture live migration is not supported. Arm64 server emphasis includes NVIDIA Grace Hopper and NVIDIA Vera; Raspberry Pi 5 has been tested as a best-effort small-board target. Mixed-architecture Continuum details →
Name resolution requirements
Use stable hostnames or addresses before enrollment. The controller must be able to resolve itself and every compute or storage worker by the names STRATUM will use.
Compute and storage workers do not need to resolve one another. Each worker only needs to resolve and reach the controller name used during enrollment and normal operation. DNS is preferred when available; static /etc/hosts entries are also suitable for controlled environments.
Procedure
Host Name Resolution Requirements
On the controller, confirm its hostname and the name-to-address mappings for the controller and every compute and storage worker. On each worker, confirm that the controller name resolves and is reachable. The example uses /etc/hosts; DNS is equally valid when it provides the same stable mappings.
Commands
Substitute your actual hostnames. DNS is equally valid; verify that each FQDN resolves to a reachable management address, not only a loopback alias. ICMP may be filtered, so a failed ping alone is not definitive.
# On the controller (example hostnames from the screenshot)
hostname
cat /etc/hosts
getent hosts ctrl1.stratum.lab
getent hosts stratum-worker1.stratum.lab
getent hosts storage.stratum.lab
# On each worker: the controller name must resolve and be reachable
getent hosts ctrl1.stratum.lab
ping -c 1 ctrl1.stratum.labThe outcome you should see
The controller resolves every configured compute and storage worker by the names STRATUM will use. Each compute and storage worker resolves and can reach the controller name used for enrollment and operation. Host resources and I/O capacity are sized for the workers and workloads planned.