From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 9A4C71FF143 for ; Mon, 19 Jan 2026 16:00:33 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D37DA21E07; Mon, 19 Jan 2026 16:00:40 +0100 (CET) Message-ID: <4b3d704a-2743-49f7-ad39-38081c20e9af@proxmox.com> Date: Mon, 19 Jan 2026 16:00:37 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Proxmox VE development discussion , Daniel Kral References: <20251215155334.476984-1-d.kral@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: <20251215155334.476984-1-d.kral@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1768834783995 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.015 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH-SERIES container/ha-manager/manager/qemu-server 00/12] HA node affinity blockers (#1497) X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" Am 15.12.25 um 4:54 PM schrieb Daniel Kral: > This patch series implements node affinity rule migration blockers > similar to the blockers introduced with resource affinity rules. > > > The node affinity rule migraton blockers prevent users from migrating HA > resources to nodes, which would make them migrate somewhere else > immediately afterwards. This includes: > > - online nodes, which are not part of the strict node affinity rule's > allowed node set at all, or > > - online nodes, which are not in the currently highest priority group of > the strict or non-strict node affinity rule and the HA resource has > failback set. > > > The first few patches are some overall cleanup for things the series > touches + deduplicating the resource_motion_info logic and sharing it > between the Manager and the public > PVE::HA::Config::get_resource_motion_info(...), as well as exposing these > in the relevant VM/LXC API handlers and web interface. > > > Since the 'cause' property in 'blocking-resources' is an enum, > qemu-server and pve-container need version bumps for pve-ha-manager as > else the API handlers would result in a schema result verification error. > > If we can spare some coupling between those, we could generate the schema > for these API handlers from the pve-ha-manager package, so future > versioned bumps are not needed anymore, but I was a bit hesitant to > implement that in the v1. There are some nits (see individual patches), but consider the series: Reviewed-by: Fiona Ebner _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel