It's probably more than you are looking for but if you are already looking at self hosting things connected with NextCloud, use NextCloud Talk. We use it for the family and it is great.
Our state is not perfect, but it feels like a country more than a state at times. We try to deal with our problems and are willing to experiment with novel solutions. It makes sense to defend our little laboratory here against willful punishment from vindictive dictators.
There were a lot of SpongeBob and Patrick interpretations, the inflatable costumes were huge
This may not be exactly what you want, but I use Apache guacamole for this. The client becomes a web browser, and a chromium based browser allows seamless bidirectional clipboard. I use Ubuntu VMs with Mate as the DM and with a few keybinds tweaked it is solid. I use tightVNC as my server which supports dynamic resize, and the soon to be released guacamole 1.6 supports sending dynamic resize (since the underlying libraries are now updated to support it; RDP in guac already supports dynamic resize). How performant is it? I have a single proxmox vm which runs 3 Minecraft instances for our server's 3 bot accounts (which just stand still) and the desktop is still navigable.
I've read extensively about that, and this thread was very helpful, and my understanding is that's still not really a DRS equivalent, but more of a recovery mode: https://forum.proxmox.com/threads/ha-cluster-resource-scheduling-filling-in-the-missing-pieces-from-the-docs.139187/
Where do you see the load balancing feature? Searching for exactly that was what got me to ProxLB. I have HA groups and fences, but that's less resource allocation than failure resolution in my experience. My cluster is 8.2.7.
I posted to the forums, but I got a "YMMV" kind of answer; the docs say it's technically unsupported: https://pve.proxmox.com/pve-docs/chapter-qm.html#_requirements
The hosts have CPUs from the same vendor with similar capabilities. Different vendor might work depending on the actual models and VMs CPU type configured, but it cannot be guaranteed - so please test before deploying such a setup in production.
I'm setting the CPU Type to x86-64-v2-AES which is the highest my westmere CPU's can do. I have a path to getting all 3 nodes to the 6525 hardware, pending some budget and some decomm's at work.
I'm battling this right now; it SHOULD work but does not work consistently. Again, homelab, not ideal environment. I'm going from 2 R710's with Xeons to a 3-node cluster with the 710's and an EPYC R6525. Sometimes VM's migrate fine, sometimes they hang and have to be full reset. Ultimately this was fine as I didn't migrate much, but then I slapped on a DRS-like thing, and I see it more. I've been collecting logs and submitting diagnostics; even pegging the VM's to a common CPU arch didn't fix it.
To that end, DRS alternatives are still mostly plugins. This was the go-to, but then it was abandoned:
https://github.com/cvk98/Proxmox-load-balancer
And now I'm getting ready to go deeper into this, but I want to resolve the migration hangs first:
I think you are looking at this wrong. Proxmox is not prod ready yet, but it is improving and the market is pushing the incumbent services into crappier service for higher prices. Broadcom is making VMware dip below the RoI threshold, and Hyper-v will not survive when it is dragging customers away from the Azure cash cow. The advantage of proxmox is that it will persist after the traditional incumbents are afterthoughts (think xenserver). That's why it is a great option for the homelab or lab environment with previous gen hardware . Proxmox is missing huge features...vms hang unpredictably if you migrate vms across hosts with different CPU architectures (Intel -> AMD), there is no cluster-wide startup order, and things like DRS equivalents are still separate plugins. That being said knowing it now and submitting feedback or patches positions you to have a solution when MS and Broadcom price you out of on-prem.
All you have to do is name tag them and they won't dig into the ground!
view more: next ›
This is a good breakdown. A firehose relay takes TB's of storage and is not practical for self-hosting, and AppView isn't hostable yet: https://alice.bsky.sh/post/3laega7icmi2q