Yes, good idea! We already thought about this during development, though we were focusing on the core feature first. Feel free to create a Bugzilla entry [0] for this in the mean time, though as this is relatively trivial to implement and as you...
Yes, some recent security fixes for the pve-manager package forced us to ship the package, which already includes the load balancer options in the web interface, earlier to all repositories, while we're still waiting to move pve-ha-manager 5.2.0...
Hi!
Recent security fixes in the pve-manager package forced us to ship this package earlier to all repositories (including the enterprise repository), which already contain the settings for the load balancer in the web interface. Though the load...
Hi!
Thanks for the feedback!
The load balancer takes both memory and CPU in account. Ad weighing, see the next paragraphs.
The load balancer can score the balancing migrations by either one of these methods.
The brute-force method (as in...
We're pleased to announce the release of Proxmox Backup Server 4.2.
This version is based on Debian 13.4 ("Trixie"), uses Linux kernel 7.0 as the new stable default for improved hardware support, and comes with ZFS 2.4 for reliable...
I proposed to change that since the failback flag's description [0] explicitly states it's only concerned about moving back to a higher priority node class, but for now it's a proposal ;).
Exactly, in the end if two nodes have the exact same...
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...
Thanks a lot for testing and sending in a report!
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...
Not directly, this will only be respected if there are no affinity rules, which prohibit this behavior. For example, if the node affinity rule in your second scenario would have been strict, then the behavior would be correct as the HA resource...
In general, there shouldn't really be a precedence as all of those conditions should hold at the same time.
The rule verification system does dismiss many types of affinity rules, which cannot be determined to be resolvable at runtime, see [0]...
The disarm-ha and arm-ha commands are mainly intended for specific maintenance tasks, where the whole cluster communication stack is temporarily unavailable or other situations, where one wants to avoid the HA stack make a node fence.
The HA...
Welcome to the Proxmox forum, Libero_AT!
For scenario 1, it seems like that the current HA stack gives more priority that the resource affinity rule holds than whether it should migrate back to its maintenance node.
For scenario 2, I assume...
Hi!
Could you post the output of pveversion -v, pct start 103 --debug and syslog which includes the starting of the container? Also what version of apparmor is running on the host?
Yes, there currently is no option to bulk add them to the HA stack, but feel free to add a feature request in our Bugzilla [0] such that we can track it there with some description what it should do.
[0]...
Hi,
you don't need to manually make rules for each VM. Just make one node affinity rule with the same node priorities you had for the HA group previously and then add all VMs that should follow those priorities to that single rule.
We're proud to present the next iteration of our Proxmox Virtual Environment platform. This new version 9.1 is the first point release since our major update and is dedicated to refinement.
This release is based on Debian 13.2 "Trixie" but we're...
Good question! But yes, in the proposed 2-node cluster setup with a QDevice, the HA Manager will only move one of the HA resources to another node and keep the other one as-is, because it is known that there aren't any other viable nodes to...