public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Daniel Kral <d.kral@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 4/5] ha: mark ha groups as deprecated and note migration to node affinity rules
Date: Mon,  4 Aug 2025 16:11:42 +0200	[thread overview]
Message-ID: <20250804141204.207216-4-d.kral@proxmox.com> (raw)
In-Reply-To: <20250804141204.207216-1-d.kral@proxmox.com>

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 <d.kral@proxmox.com>
---
Alternatively, we could already remove the HA groups section now/after
the next patch, which replaces any references to groups in the remaining
text in ha-manager.adoc (AFAIK there are still some minor references in
pve-docs, e.g. ha-groups-opts.adoc, references to
/etc/pve/ha/groups.cfg, etc.).

 ha-manager.adoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/ha-manager.adoc b/ha-manager.adoc
index e18a14d..ffab83c 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


  parent reply	other threads:[~2025-08-04 14:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04 14:11 [pve-devel] [PATCH docs 1/5] ha: affinity rules: simplify overly verbose rule conflicts and errors section Daniel Kral
2025-08-04 14:11 ` [pve-devel] [PATCH docs 2/5] ha: rules: update about mixed usage of node and resource affinity rules Daniel Kral
2025-08-04 15:09   ` Hannes Duerr
2025-08-05  7:15     ` Daniel Kral
2025-08-04 14:11 ` [pve-devel] [PATCH docs 3/5] ha: rules: document crs behavior for split positive resource affinity Daniel Kral
2025-08-05  7:42   ` Michael Köppl
2025-08-05  7:50     ` Daniel Kral
2025-08-04 14:11 ` Daniel Kral [this message]
2025-08-04 14:11 ` [pve-devel] [PATCH docs 5/5] ha: replace in-text references to ha groups with ha rules Daniel Kral
2025-08-04 15:24   ` Hannes Duerr
2025-08-05  7:39     ` Daniel Kral
2025-08-05  7:41   ` Michael Köppl
2025-08-05  7:47 ` [pve-devel] [PATCH docs 1/5] ha: affinity rules: simplify overly verbose rule conflicts and errors section Michael Köppl
2025-08-05  8:01 ` [pve-devel] applied: " Daniel Kral

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250804141204.207216-4-d.kral@proxmox.com \
    --to=d.kral@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal