From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Daniel Kral" <d.kral@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH docs 12/18] ha-manager: crs: use headings for the scheduling points
Date: Mon, 13 Apr 2026 17:52:35 +0200 [thread overview]
Message-ID: <DHS5BU4DLUOA.18W7N3FAHI5UN@proxmox.com> (raw)
In-Reply-To: <20260409114224.323102-13-d.kral@proxmox.com>
noticed 2 typos, mentioned inline
On Thu Apr 9, 2026 at 1:41 PM CEST, Daniel Kral wrote:
> This is in preparation to be able to extend the existing entries with
> more information and allows users to make permalinks to the specific
> scheduling points.
>
> Signed-off-by: Daniel Kral <d.kral@proxmox.com>
> ---
> ha-manager.adoc | 61 +++++++++++++++++++++++++++----------------------
> 1 file changed, 34 insertions(+), 27 deletions(-)
>
> diff --git a/ha-manager.adoc b/ha-manager.adoc
> index 716e77e..7d4bc44 100644
> --- a/ha-manager.adoc
> +++ b/ha-manager.adoc
> @@ -1474,38 +1474,45 @@ CRS Scheduling Points
> In every HA Manager round, the CRS checks whether any HA resources need a new
> node placement, which can be caused by any of the following scheduling points:
>
> -- HA resource recovery (always active). When a node with active HA resources
> - fails, all its HA resources need to be recovered to other nodes. The CRS
> - algorithm will be used here to balance that recovery over the remaining nodes.
> +HA resource recovery (always active)
> +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> -- HA rule config changes (always active). If a rule emposes different
s/emposes/imposes
> - 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:
> +When a node with active HA resources fails, all its HA resources need to be
> +recovered to other nodes. The CRS algorithm will be used here to balance that
> +recovery over the remaining nodes.
>
> -** 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 rule config changes (always active)
> +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> -** Positive resource affinity rules: If a positive resource affinity rule is
> - created or HA resources are added to an existing positive resource affinity
> - rule, the HA stack will use the CRS algorithm to ensure that these HA
> - resources are moved to a common node.
> +If a rule emposes different constraints on the HA resources, the HA stack will
s/emposes/imposes
> +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:
[snip]
next prev parent reply other threads:[~2026-04-13 15:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 11:41 [PATCH-SERIES manager/docs 00/18] crs docs updates + load balancer ui and docs followup Daniel Kral
2026-04-09 11:41 ` [PATCH manager 01/18] ui: form/CRSOptions: add missing edit modal title Daniel Kral
2026-04-09 11:41 ` [PATCH manager 02/18] ui: form/CRSOptions: rename HA Scheduling to Scheduling Mode Daniel Kral
2026-04-09 11:41 ` [PATCH manager 03/18] ui: form/CRSOptions: replace HA service term with HA resource Daniel Kral
2026-04-09 11:41 ` [PATCH manager 04/18] ui: form/CRSOptions: use view model for auto rebalancing option Daniel Kral
2026-04-09 11:41 ` [PATCH manager 05/18] ui: form/CRSOptions: allow auto rebalancing only for static and dynamic mode Daniel Kral
2026-04-13 16:01 ` Michael Köppl
2026-04-14 7:18 ` Daniel Kral
2026-04-14 7:32 ` Michael Köppl
2026-04-14 7:39 ` Daniel Kral
2026-04-09 11:41 ` [PATCH docs 06/18] ha-manager: crs: replace service term with HA resource Daniel Kral
2026-04-09 11:41 ` [PATCH docs 07/18] ha-manager: crs: remove note about manual changes to datacenter config Daniel Kral
2026-04-10 8:17 ` Shannon Sterz
2026-04-10 11:18 ` Daniel Kral
2026-04-10 11:37 ` Shannon Sterz
2026-04-09 11:41 ` [PATCH docs 08/18] ha-manager: crs: improve introduction Daniel Kral
2026-04-09 11:41 ` [PATCH docs 09/18] ha-manager: crs: introduce crs scheduling mode section Daniel Kral
2026-04-09 11:41 ` [PATCH docs 10/18] ha-manager: crs: generalize the description for basic and static load modes Daniel Kral
2026-04-09 11:41 ` [PATCH docs 11/18] ha-manager: crs: remove HA group config from scheduling points list Daniel Kral
2026-04-09 11:41 ` [PATCH docs 12/18] ha-manager: crs: use headings for the scheduling points Daniel Kral
2026-04-13 15:52 ` Michael Köppl [this message]
2026-04-09 11:41 ` [PATCH docs 13/18] ha-manager: crs: reword the rebalance on start scheduling point Daniel Kral
2026-04-13 15:53 ` Michael Köppl
2026-04-09 11:41 ` [PATCH docs 14/18] ha-manager: crs: add more information about rebalance on start in its section Daniel Kral
2026-04-09 11:41 ` [PATCH docs 15/18] ha-manager: crs: change crs modes to include all active guests Daniel Kral
2026-04-09 11:41 ` [PATCH docs 16/18] ha-manager: crs: add dynamic load scheduler Daniel Kral
2026-04-09 11:41 ` [PATCH docs 17/18] screenshots: update crs datacenter options screenshot Daniel Kral
2026-04-09 11:41 ` [PATCH docs 18/18] ha-manager: crs: add load balancer section Daniel Kral
2026-04-13 16:11 ` Michael Köppl
2026-04-14 12:03 ` Dominik Rusovac
2026-04-13 16:11 ` [PATCH-SERIES manager/docs 00/18] crs docs updates + load balancer ui and docs followup Michael Köppl
2026-04-14 7:24 ` Daniel Kral
2026-04-15 9:19 ` superseded: " 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=DHS5BU4DLUOA.18W7N3FAHI5UN@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=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