In short, I really just want to be able to have 2 clusters, one low and one high power, with one webUI and the ability to manually migrate from one pve host to another.
I want the low power pve host always on, while the other host can only be up when I need it.
Reading other folks posts, using an external QDevice is the way to do this, but I can't help it being the homelab hack I am... what if I just virtualize the QDevice?
As I (loosely) understand it, this might allow for the behavior I want, but would prevent the low power host from booting up properly alone (running vms at boot etc) when it does eventually power cycle...
so when a single host boots and doesnt see quorum, will:
`pve expected 1 && qm start <vmID> && pve expected 2`
potentially do the trick?
if not, then another external little linux box will have to be the solution, I just want to know if I can get around it with a very non-production homelab applications...
thanks for reading
I want the low power pve host always on, while the other host can only be up when I need it.
Reading other folks posts, using an external QDevice is the way to do this, but I can't help it being the homelab hack I am... what if I just virtualize the QDevice?
As I (loosely) understand it, this might allow for the behavior I want, but would prevent the low power host from booting up properly alone (running vms at boot etc) when it does eventually power cycle...
so when a single host boots and doesnt see quorum, will:
`pve expected 1 && qm start <vmID> && pve expected 2`
potentially do the trick?
if not, then another external little linux box will have to be the solution, I just want to know if I can get around it with a very non-production homelab applications...
thanks for reading