Re: [PATCH-SERIES ha-manager/manager 0/3] fix #7557: introduce 'auto-rebalance' property

["Daniel Kral" <d.kral@proxmox.com>]

On Mon May 11, 2026 at 5:57 PM CEST, Dominik Rusovac wrote:
> # TL;DR 
> Add 'auto-rebalance' property to HA resources config, which gives users
> control over which HA resources may be moved by dynamic CRS during
> automatic rebalancing.
>
> # Details
> The 'auto-rebalance' flag is set to true by default. As requested by [0],
> disabling 'auto-rebalance' for some HA resource, say vm:100, means that vm:100
> will be disregarded as a migration candidate during auto-rebalancing. Any HA
> resource with a positive affinity for vm:100 will be disregarded too.
>
> # Summary of Changes
> This series:
> - introduces property to control whether an HA resource may be migrated during
>   automatic rebalancing;
> - adds corresponding flag to PVE UI.
>
> # Refs
> [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7557

Tested the series and it works just as expected:

- only a single HA resource with auto-rebalance cleared; set
  imbalance-threshold to 0.1 and imbalance-margin to 0.05, put no load
  on node3, some load on node2 and a lot of load with a non-HA VM and
  the HA resource from above, but it was never moved to the other nodes;
  it was moved to node3 as soon as I set auto-rebalance again

- tested the same with a positive resource affinity rule with that HA
  resource and another new HA resource and they never moved away unless
  I set the auto-rebalance option for all again

Nice work, thanks for the quick patch series!

Would be great to document this in the documentation as well so users
are aware especially that if such HA resources are in a resource
affinity rule, that they make the whole resource bundle immovable. But
this can also be done as a follow-up.

Consider this as:

Tested-by: Daniel Kral <d.kral@proxmox.com>