From: "Daniel Kral" <d.kral@proxmox.com>
To: "Daniel Kral" <d.kral@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH-SERIES ha-manager v2 00/10] include non-HA resources in usage accounting
Date: Thu, 19 Mar 2026 17:56:54 +0100 [thread overview]
Message-ID: <DH6X1GK1YI3W.24PDWP36RSCVU@proxmox.com> (raw)
In-Reply-To: <20260319164047.642936-1-d.kral@proxmox.com>
On Thu Mar 19, 2026 at 5:33 PM CET, Daniel Kral wrote:
> This series is split out from [0] to make the static/dynamic load
> balancer series a little more straight forward to reason through.
>
> This series adds any running non-HA resource into the existing basic and
> static usage scheduler accounting to base decisions on the usage of the
> whole cluster instead of just the HA resources.
>
> For clusters where every guest is configured as a HA resource nothing
> should change.
>
> I tested a few simple cases in a 3 node cluster for both the basic and
> static usage which are variations of:
>
> - 1 running HA resource on each node, starting them on any node (with
> homogeneous nodes and guests) will rebalance them on the
> alphabetically first node as before
> - 1 running HA resource on node1, running 3 non-HA resources on node2,
> starting another HA resource on node1 will rebalance it to node3
> - 3 non-HA resources on node1, starting a HA resource on node1 will
> rebalance it to node2
> - non-running HA and non-HA resources are excluded from the usage
> accounting
> - starting non-HA resources doesn't have any effect obviously
>
Sorry for the noise, there are only two changes in the series in patch
#9:
- removing the duplicate $sid as suggested by @Thomas, and
- adding constants for indexing the rrd status indirectly suggested by
@Thomas in a later patch in the series.
Otherwise the series is identical to the patches from [0].
> [0] https://lore.proxmox.com/pve-devel/20260217141437.584852-1-d.kral@proxmox.com/
prev parent reply other threads:[~2026-03-19 16:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 16:33 Daniel Kral
2026-03-19 16:33 ` [PATCH ha-manager v2 01/10] rename static node stats to be consistent with similar interfaces Daniel Kral
2026-03-19 16:33 ` [PATCH ha-manager v2 02/10] resources: remove redundant load_config fallback for static config Daniel Kral
2026-03-19 16:33 ` [PATCH ha-manager v2 03/10] remove redundant service_node and migration_target parameter Daniel Kral
2026-03-19 16:33 ` [PATCH ha-manager v2 04/10] factor out common pve to ha resource type mapping Daniel Kral
2026-03-19 16:33 ` [PATCH ha-manager v2 05/10] derive static service stats while filling the service stats repository Daniel Kral
2026-03-19 16:33 ` [PATCH ha-manager v2 06/10] test: make static service usage explicit for all resources Daniel Kral
2026-03-19 16:33 ` [PATCH ha-manager v2 07/10] make static service stats indexable by sid Daniel Kral
2026-03-19 16:33 ` [PATCH ha-manager v2 08/10] move static service stats repository to PVE::HA::Usage::Static Daniel Kral
2026-03-19 16:33 ` [PATCH ha-manager v2 09/10] usage: augment service stats with node and state information Daniel Kral
2026-03-19 16:34 ` [PATCH ha-manager v2 10/10] include running non-HA resources in the scheduler's accounting Daniel Kral
2026-03-19 16:56 ` Daniel Kral [this message]
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=DH6X1GK1YI3W.24PDWP36RSCVU@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