dakralex's latest activity
-
dakralex replied to the thread [SOLVED] HA-Migration auf vorherige Node.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... -
dakralex reacted to mkoeppl's post in the thread [SOLVED] HA-Migration auf vorherige Node with
Like.
Hallo, ergänzend zu der Antwort von @UdoB sei der Vollständigkeit halber noch ergänzt, dass Rules ebenfalls eine strict Option bieten. Siehe hier. Intern werden bei einer Node Affinity Rule, die nicht strict ist, Nodes, die nicht Teil der Node... -
Thanks! Done: https://bugzilla.proxmox.com/show_bug.cgi?id=7557
-
dakralex replied to the thread ha-manager and VM's with host passthrough.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...
-
dakralex replied to the thread ha-manager and VM's with host passthrough.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...
-
dakralex replied to the thread Disable / Enable ha-manager resource-affinity rules via CLI not working anymore (after upgrading to 9.1.9).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...
-
dakralex replied to the thread Questions about the dynamic CRS.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...
-
dakralex replied to the thread Questions about the dynamic CRS.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...
-
dakralex replied to the thread Questions about the dynamic CRS.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...
-
dakralex replied to the thread PVE 9.1.9 cannot enable new cluster resource scheduling (crs) dynamic option.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...
-
dakralex replied to the thread Questions about the dynamic CRS.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...
-
dakralex replied to the thread Clarification related to HA Maintenance Mode/Affinity Rules.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...
-
dakralex replied to the thread Proxmox pve-manager 9.1.8 / pve-ha-manager 5.2.0 [Dynamic load intro].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...
-
dakralex replied to the thread Proxmox pve-manager 9.1.8 / pve-ha-manager 5.2.0 [Dynamic load intro].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...
-
dakralex replied to the thread Clarification related to HA Maintenance Mode/Affinity Rules.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...
-
dakralex replied to the thread Clarification related to HA Maintenance Mode/Affinity Rules.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]...
-
dakralex replied to the thread disarm-ha and arm-ha commands.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...
-
dakralex replied to the thread Clarification related to HA Maintenance Mode/Affinity Rules.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...
-
dakralex replied to the thread [Solved] Recent updates caused problem with migration.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?