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 C1EFA1FF16B for ; Tue, 29 Jul 2025 20:01:51 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id AA96F1A378; Tue, 29 Jul 2025 20:01:52 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Date: Tue, 29 Jul 2025 20:01:01 +0200 Message-ID: <20250729180107.428855-22-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250729180107.428855-1-d.kral@proxmox.com> References: <20250729180107.428855-1-d.kral@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753812064033 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.013 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 Subject: [pve-devel] [PATCH docs v4 2/2] ha: crs: add effects of ha node affinity rule on the crs scheduler 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" Add information about the effects that HA rules and HA Node Affinity rules have on the CRS scheduler and what can be expected by a user if they do changes to them. Signed-off-by: Daniel Kral --- ha-manager.adoc | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/ha-manager.adoc b/ha-manager.adoc index 3b3f87d..20eeb88 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -1193,6 +1193,16 @@ The CRS is currently used at the following scheduling points: new target node for the HA services in that group, matching the adapted priority constraints. +- HA rule config changes (always active). If a rule emposes different + constraints on the HA resources, the HA stack will use the CRS algorithm to + find a new target node for the HA resources affected by these rules depending + on the type of the new rules: + +** Node affinity rules: If a node affinity rule is created or HA resources/nodes + are added to an existing node affinity rule, the HA stack will use the CRS + algorithm to ensure that these HA resources are assigned according to their + node and priority constraints. + - HA service stopped -> start transition (opt-in). Requesting that a stopped service should be started is an good opportunity to check for the best suited node as per the CRS algorithm, as moving stopped services is cheaper to do -- 2.47.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel