Proxmox pve-manager 9.1.8 / pve-ha-manager 5.2.0 [Dynamic load intro]

[atromitos]

Hello Proxmox

Thank you for introducing the "DRS" feature to Proxmox cluster. When I saw it in the non-subscription repo, I decided to test it.

In my 5 node test cluster, in order to create an imbalance, I live-migrated all my VMs to 1 node only. I disabled my anti-affinity (keep-separated) rules while keeping HA scheduling to basic (default). Once verified that they are all running on 1 node only, I changed Ha scheduling to:

- dynamic load
- activated "Automatically re-balance HA resources", left re-balancing method to: Default (bruteforce) - I haven't tried TOPSIS yet - no documentation for the dialogue as of yet when clicking on Help in the dialogue but I am sure it's coming in 9.2)
- left all other parameters intact in the dialogue

Observation:
- 1 by 1 VMs started migrating to other nodes (this was on day1; I left this config soak)
- day 2 - CRS migrated several vms during the night

I have observed no errors so far. I hope this helps as a feedback to you and other fellow users.

I have been wondering is it possible to add, at the bottom pane where the tasks can be seen, something like "Migrated - initiated by CRS" so that there is a distinctiveness when a human user live migrates vs system? Also what happens if there are keep-separated AA resource rules enabled and Dynamic Load is active?

Thank you!

 

[dakralex]

Thanks a lot for testing and sending in a report!

- activated "Automatically re-balance HA resources", left re-balancing method to: Default (bruteforce) - I haven't tried TOPSIS yet - no documentation for the dialogue as of yet when clicking on Help in the dialogue but I am sure it's coming in 9.2)

There is a patch series in review, which overhauls the CRS section itself and adds documentation for the new load balancing system here [0], but this will certainly be available before or in the Proxmox VE 9.2 release. External feedback on these patches are also very welcome if things could be made clearer or certain things should be elaborated on more!

Also what happens if there are keep-separated AA resource rules enabled and Dynamic Load is active?

The load balancer always makes sure that the initiated migrations follow the affinity rules (both node and positive/negative resource affinity rules).

For example, an HA resource in a node affinity rule with three nodes can only be placed on these three nodes. Furthermore, since HA resources in a positive resource affinity rules are always moved together, these are considered as a single HA resource for their CPU/memory usage statistics to predict on which nodes these HA resources are best placed on.

The "HA Scheduling Mode" is a separate option, which allows setting which type of usage data is used for these calculations. The automatic load balancer requires either the Static-Load mode, which considers the configured maximum quotas for the HA resources, or the Dynamic-Load mode, which considers the current usage data for the HA resources.

[0] https://lore.proxmox.com/pve-devel/20260415091635.162224-20-d.kral@proxmox.com/

 

[dakralex]

I have been wondering is it possible to add, at the bottom pane where the tasks can be seen, something like "Migrated - initiated by CRS" so that there is a distinctiveness when a human user live migrates vs system?

Thanks for the input! This should be doable, but since we haven't tracked whether migrations are initiated by a user or some automatic mechanism yet, this should be tracked in a separate Bugzilla entry, so feel free to create one for this here [0]. This could also be related to another feature request regarding the tracking between the HA stack's and qemu-server/pve-container tasks [1].

[0] https://bugzilla.proxmox.com/enter_bug.cgi?product=pve&component=HA
[1] https://bugzilla.proxmox.com/show_bug.cgi?id=6220