From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 560DA1FF136 for ; Mon, 04 May 2026 13:12:37 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 339B71A47A; Mon, 4 May 2026 13:12:37 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Subject: [PATCH docs 2/2] ha-manager: add requirements for ha-managed vms and containers Date: Mon, 4 May 2026 13:11:55 +0200 Message-ID: <20260504111159.183163-3-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260504111159.183163-1-d.kral@proxmox.com> References: <20260504111159.183163-1-d.kral@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1777893018528 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.078 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: FAJTTKHHC7C7LMLLFCSTW4XT4BOADZC7 X-Message-ID-Hash: FAJTTKHHC7C7LMLLFCSTW4XT4BOADZC7 X-MailFrom: d.kral@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: The HA Manager implicitly requires certain conditions that VMs and containers need to fulfill to be handled correctly by the HA Manager. Make the most important conditions explicit by writing them out in the HA resources section and add a paragraph what role HA rules play here to accomodate for HA resources, which do not meet all of these requirements. Signed-off-by: Daniel Kral --- ha-manager.adoc | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/ha-manager.adoc b/ha-manager.adoc index 6bf4e69..599622a 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -135,6 +135,26 @@ consists of the resource type and a type-specific ID, which is the VMID for VMs and containers. For example, for the VM with VMID `100`, the service ID is `vm:100`. +In general, HA resources need to be setup in such a way, so that they are +able to run on any cluster node. Therefore, a VM or container should meet +the following requirements before it is added as an HA resource: + +* use options, which are compatible on all nodes + +* only use shared storage, which are available on all nodes + +* only use network interfaces, which are available on all nodes + +* only use device passthroughs, which are available on all nodes + +If a VM or container cannot fully meet these requirements, it can still +be possible to configure them as HA resources by encoding the deviations +from these requirements as xref:ha_manager_rules[HA rules]. For example, +if the device passthrough for an HA resource is only available to some +of the cluster nodes, then the HA resource must be constrained to these +cluster nodes by a strict +xref:ha_manager_node_affinity_rules[node affinity rule]. + Management Tasks ---------------- -- 2.47.3