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 6348A1FF16F for ; Tue, 5 Aug 2025 09:58:27 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 04BFC8490; Tue, 5 Aug 2025 09:59:51 +0200 (CEST) From: Daniel Kral To: pve-devel@lists.proxmox.com Date: Tue, 5 Aug 2025 09:58:38 +0200 Message-ID: <20250805075944.35405-3-d.kral@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250805075944.35405-1-d.kral@proxmox.com> References: <20250805075944.35405-1-d.kral@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1754380768443 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.012 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: [pve-devel] [PATCH docs v2 3/4] ha: mark ha groups as deprecated and note migration to node affinity rules 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" As the migration is handled automatically by the HA Manager now instead of manual user migration, the notice should be placed in the HA Groups section instead. Signed-off-by: Daniel Kral --- changes since v1: - none ha-manager.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/ha-manager.adoc b/ha-manager.adoc index 434c33f..705f522 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -594,6 +594,9 @@ The above config was generated using the `ha-manager` command-line tool: Groups ~~~~~~ +NOTE: HA Groups are deprecated and migrated to HA Node Affinity rules since +Proxmox VE 9.0. + [thumbnail="screenshot/gui-ha-manager-groups-view.png"] The HA group configuration file `/etc/pve/ha/groups.cfg` is used to @@ -700,9 +703,6 @@ on the same node. Node Affinity Rules ^^^^^^^^^^^^^^^^^^^ -NOTE: HA Node Affinity rules are equivalent to HA Groups and will replace them -in an upcoming major release. - By default, a HA resource is able to run on any cluster node, but a common requirement is that a HA resource should run on a specific node. That can be implemented by defining a HA node affinity rule to make the HA resource -- 2.47.2 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel