Preferred multi-site build?

[pcericm]

I've been currently building out a local proxmox cluster for my homelab and was curious on what would be the best approach to expanding the cluster to a second location (cabin) where I could run some local services (dns, frigate, a livestream service, etc) and manage it under the same management pane.

The local cluster is a 3-node system with a bunch of dedicated networks for running corosync and synchronization for a nvme-only cephfs object store. Each site will have a NAS set-up that replicates 100% of it's content (site A->B) and could be used for VM storage if necessary.

Now the question is could two additional servers (with potentially a raspberry-pi for quorum state but likely not really necessary) be added to my current cluster but operate within their own realm/synchronization domain at site B? It will have a much more basic network config and I don't expect that any services from the local cluster would fail-over to the remote site (and vice-versa), but being able to manage and keep configuration in one system would be pretty ideal. Or is the best approach to just deploy site B as it's own cluster and deal with it that way? I did some looking into cluster management and I don't really see much in the way of managing more than 1 cluster within the proxmox enviornment.

Thanks for any input.

 

[aaron]

If you span the cluster to the other location, there is no need for a QDevice, as they will be part of the cluster and contribute to the votes. This is most likely not a good idea, as the question is how much latency you have and how stable that connection is.

Create a separate cluster in the other location to keep concerns separate.

There is currently no official unified UI to manage multiple cluster, but currently worked on. Until then you will have to connect to each individual cluster.

 

[pcericm]

If you span the cluster to the other location, there is no need for a QDevice, as they will be part of the cluster and contribute to the votes. This is most likely not a good idea, as the question is how much latency you have and how stable that connection is.

Create a separate cluster in the other location to keep concerns separate.

There is currently no official unified UI to manage multiple cluster, but currently worked on. Until then you will have to connect to each individual cluster.

Yeah I figured the latency might be a bit of an issue (it's about 20-30ms). It's only as stable as Comcast is reliable ;-) I'll keep them separate and look forward to a future enhancement through proxmox to manage them. Thanks!