Recent content by dakralex

Hi! In general, the cluster nodes should have the same package versions installed to function properly. The HA Manager also has some basic assumptions, as is described in the relevant documentation section [0]. Specifically, if specific nodes cannot satisfy the dependency of a VM (here: the...

Hi! You can configure these with the environment variables PBS_RESTORE_FETCH_CONCURRENCY for the amount of parallel chunk fetches and PBS_RESTORE_MAX_THREADS for the maximum amount of threads. You should be able to use these in front of the qmrestore command, for example with the default...

Hi! Bitte poste noch den Output von den folgenden Kommandos: $ pveversion -v $ pct config 5006 $ pct start 5006 --debug

Hi! 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 (including the enterprise repository), while we're still waiting to move pve-ha-manager 5.2.0 and...

Just for reference, I opened a Bugzilla entry for this [0] with a reference to this forum post to not loose track of this. [0] https://bugzilla.proxmox.com/show_bug.cgi?id=7567

Right, the failback flag does only control if an HA resource is in a node affinity rule (formerly, HA groups) and is in a lower-priority node class. As soon as the higher-priority node class gets back online again, the HA resource will automatically move back to that node. Otherwise, it will...

I'll answer both questions in one, because they're quite related: The scheduling mode (basic, static-load, dynamic-load) specifies which measure is used to compare nodes and HA resources against each other: For the basic mode, it's simply how many running guests are on the nodes. For the...

Im Moment gibt es kein implizites automatisches Verteilen zwischen den Regelmitgliedern. Jedoch gibt es ab Proxmox VE 9.0 die strikt negativen HA Resource Affinity Rules, welche es ermöglichen, dass mehrere HA Ressourcen auf verschiedenen Knoten platziert werden müssen. Es gibt ein ähnlichen...

Not exactly, the node affinity rules define where an HA resource can currently move. For example, if the HA resource is in a strict node affinity rule with only one node, then it will only stay there. This makes the HA resource essentially immovable, even during a recovery because of a fenced...

Hi! Thanks for the feedback! Generally, an HA resource must be able to run on any node and also be migratable to any node. Otherwise, one needs to encode these constraints in HA rules. I've sent in a patch [0] to add notes about this so that it is more obvious as it was rather an implicit...

Hi! Unfortunately, this is a bug, which was introduced in pve-ha-manager 5.1.2, but is fixed for the current pve-ha-manager 5.2.0, which is on the pve-test and pve-no-subscription repositories. If you currently cannot update to this package version, it should work to add the resources option...

Thanks for the feedback! We also thought about including more terms to the "cost function" of a migration, though we mainly focused on the core feature first. The current load balancing implementation focuses on reducing the imbalance between the nodes as much as possible. The larger the...

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 said causes downtime while moving and restarting...

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 and pve-cluster 9.1.2 to the enterprise...

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 balancing functionality from pve-ha-manager...