I setup HA on a four-node cluster. On node1 I created 3 CT's and configured them for HA. I then stopped rgmanager on node1 to test relocation. All three CT's were migrated to node2. This seems suboptimal. Is there any way to cause them to be migrated round-robin (first CT to node2, second to node3, etc)? I'm imagining a scenario where a node fails, and all its CT's are migrated to a single node, causing it to be overloaded when there are plenty of resources available on other nodes.
Ideally, it would use SNMP or something to prefer the least-loaded nodes, but even if it were to simply round-robin the relocation, it would be better than simply relocating everything to a single node.
I found an old project, LBVM, that does actual load balancing for rgmanager, but it appears quite outdated and I don't know how it would integrate with PVE in any case.
If I'm willing to hack a bit, where would I start? I took a look at the scripts under /usr/share/cluster but I couldn't figure out how they are related. The pvevm script doesn't appear to be involved in the preferred node decision. Would this mean changing rgmanager itself, or can it be done using rgmanager event scripting?
Ideally, it would use SNMP or something to prefer the least-loaded nodes, but even if it were to simply round-robin the relocation, it would be better than simply relocating everything to a single node.
I found an old project, LBVM, that does actual load balancing for rgmanager, but it appears quite outdated and I don't know how it would integrate with PVE in any case.
If I'm willing to hack a bit, where would I start? I took a look at the scripts under /usr/share/cluster but I couldn't figure out how they are related. The pvevm script doesn't appear to be involved in the preferred node decision. Would this mean changing rgmanager itself, or can it be done using rgmanager event scripting?