What about OpenStack, or even CloudStack?

This seems to be more of a VCenter counterpart, vcloud director was more about the multi tenancy (and multi cloud).

But a great step nonetheless! Hope they grow too.

I use this bookmarklet on phone when I encounter a page like that and it usually make things better.

javascript:(function(){document.head.insertAdjacentHTML('beforeend','<meta name="viewport" content="width=device-width"/><style>body{word-break:break-word;-webkit-text-size-adjust:none;text-size-adjust:none;}</style>');})();

It does three things, It adds a viewport meta tag for a proper mobile scaling. Prevents long words/URLs from breaking thr page layout and disables automatic font size adjustment on Safari in landscape mode

You can absolutely run it in a VM. I spun up an instance the other day in a VM and have had no problems.

I assume you want to run it outside the clusters it manages.

We run proxmox on a bunch of hardware servers, but for "homelab" we use Ubuntu on ZFS + Incus cluster. What I look at is IncusOS: a radically new approach to base cluster OS: no SSH, no configuration. So far it looks too radical, but eventually I see that as the only way to go for somebody who has a "zoo" of servers behind Tailscale: just base OS which upgrades safely, immutable and encrypted, without any unique configuration. The vision looks beautiful.

Yes! In this great video from level1techs Wendel walks around in a brand new ai gpu datacenter, an engineer tells what they use for all the normal stuff :-)

Inside the Modern Data Center! SuperClusters at Applied Digital https://youtu.be/zcwqTkbaZ0o?si=V2uPScjyN_sJcIh7&t=696

The company I work for is migrating a few hundred VMWare hosts to Proxmox due to licensing and cost considerations. In our case, since most of the hosts are not clustered, the migration process is quite straightforward. The built-in migration tool proves to be exceptionally effective.

> I've kind of wanted to build a three node cluster with some low end stuff to expand my knowledge of it. Now they have a datacenter controller.

You can set up a cluster to play with multiple nodes without the just-announced PDM 1.0. Or you can use PDM to manage three stand alone nodes.

If you want to do both, perhaps a 3-node cluster plus a 1-node stand alone with a PDM 'overlay'. So just a +1 versus a 2x.

Both my current org and previous org (large) have mentioned it many times as an option, but both ended up choosing other commercial alternatives: HyperV and XenServer.

I think the missing datacenter manager was causing a lot of hesitation for those that don't manage via automation

> I'd need to build twice the nodes.

Why twice the nodes? The manager is optional -- but do you need multiples?

Also, when I looked into clusters (that I haven't implemented,) I did see qdevices. It's a way to have a cheap and weak third node just to break ties.

I set it up for my small company 5 years ago. Couldn't be happier with it honestly.

I've heard good things about XCP-ng as well and tried it out at home and proxmox seems much easier to use out of the box. Not saying XCP-ng is bad just that it wasn't as intuitive to me as proxmox was when we were moving away from vmware

And there's also Triton[0] and vanilla SmartOS[1] it's based on

[0] https://github.com/TritonDataCenter/triton

[1] https://docs.smartos.org/

K8S doesn't scale nearly as well due to etcd and latency sensitivity. Multi-site K8S is messy. The whole K8S model is overly-complex for what almost any org actually needs. Proxmox, Incus, and Nomad are much better designed for ease of use and large scale.

That said, I still run K8S in my homelab. It's an (unfortunately) important skill to maintain, and operators for Ceph and databases are worth the up-front trouble for ease of management and consumption.