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: [PATCH docs v2 11/12] ha-manager: rules: adapt rule configuration examples
Date: Tue,  2 Jun 2026 12:01:15 +0200	[thread overview]
Message-ID: <20260602100226.180071-12-d.kral@proxmox.com> (raw)
In-Reply-To: <20260602100226.180071-1-d.kral@proxmox.com>

The section config writer does order the options slightly different, so
adapt these to make the configuration examples deterministic.

Signed-off-by: Daniel Kral <d.kral@proxmox.com>
---
changes since v1:
- new

 ha-manager.adoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/ha-manager.adoc b/ha-manager.adoc
index 479b539..802e5b9 100644
--- a/ha-manager.adoc
+++ b/ha-manager.adoc
@@ -763,13 +763,13 @@ The above commands create the following rules in the rules configuration file:
 .Node Affinity Rules Configuration Example (`/etc/pve/ha/rules.cfg`)
 ----
 node-affinity: ha-rule-vm100
-        resources vm:100
         nodes node1
+        resources vm:100
         strict 1
 
 node-affinity: priority-cascade
-        resources vm:200,ct:300
         nodes node1:2,node2:1,node3:1,node4
+        resources vm:200,ct:300
 ----
 
 Node Affinity Rule Properties
@@ -832,12 +832,12 @@ The above commands created the following rules in the rules configuration file:
 .Resource Affinity Rules Configuration Example (`/etc/pve/ha/rules.cfg`)
 ----
 resource-affinity: keep-together
-        resources vm:100,vm:200
         affinity positive
+        resources vm:100,vm:200
 
 resource-affinity: keep-separate
-        resources vm:200,ct:300
         affinity negative
+        resources vm:200,ct:300
 ----
 
 Interactions between Positive and Negative Resource Affinity Rules
-- 
2.47.3





  parent reply	other threads:[~2026-06-02 10:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 10:01 [PATCH-SERIES docs/ha-manager/manager v2 00/12] Negative Node Affinity Rules Daniel Kral
2026-06-02 10:01 ` [PATCH ha-manager v2 01/12] rules: node affinity: add affinity property to node affinity rules Daniel Kral
2026-06-02 10:01 ` [PATCH ha-manager v2 02/12] rules: rename ambiguous argument nodes to cluster nodes Daniel Kral
2026-06-02 10:01 ` [PATCH ha-manager v2 03/12] rules: node affinity: implement negative node affinity rules Daniel Kral
2026-06-02 10:01 ` [PATCH manager v2 04/12] ui: ha: node affinity: handle non-existent nodes Daniel Kral
2026-06-02 10:01 ` [PATCH manager v2 05/12] ui: ha: node affinity: do update node selection all at once Daniel Kral
2026-06-02 10:01 ` [PATCH manager v2 06/12] ui: ha: node affinity: move node priority selector into separate component Daniel Kral
2026-06-02 10:01 ` [PATCH manager v2 07/12] ui: ha: node affinity: allow setting affinity for node affinity rules Daniel Kral
2026-06-02 10:01 ` [PATCH manager v2 08/12] ui: ha: node affinity: do not send default node affinity rule values Daniel Kral
2026-06-02 10:01 ` [PATCH docs v2 09/12] ha-manager: rules: use the correct article for terms starting with HA Daniel Kral
2026-06-02 10:01 ` [PATCH docs v2 10/12] ha-manager: rules: improve resource affinity rule short description Daniel Kral
2026-06-02 10:01 ` Daniel Kral [this message]
2026-06-02 10:01 ` [PATCH docs v2 12/12] ha-manager: rules: add negative node affinity rule descriptions 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=20260602100226.180071-12-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