Hello,
I use pve to virtualize my opnSense router, I'm about to install and configure a second machine with another pve and another virtual router that will use CARP to do failover of the first virtual router.
I feel there is no need for me to use pve cluster features, especially since both virtual router should be 2 distinct VM running each on a distinct pve host.
No other VM should be automatically migrated from one pve host to the other when it fails...
Actually, I have one CT that is running traefik for me and is my loadbalancer/proxy to answer sollicitation from WAN clients, this CT would benefit from keeping running.
But in fact, this CT cannot be the same on both pve hosts since the failover host is much lower power/RAM.
So what I should really do is to have another CT running a smaller version of traefik on my failover pve, and spin this up when the main pve is down, just to keep some proxying working but not the full extent of what my traefik/docker CT is doing on my main pve.
I'm not sure having a pve cluster is really necessary especially since I have no physical fencing and I would turn to a raspberry pi to be the service to achieve corum.
I tend towards setting up a VIP for my traefik host and keep both the main and the failover CT running all the time.
Would welcome any advice on why I should be using pve clustering.
I see the raspberry qdevice as the main advantage, but I'm not sure that a pve cluster is well suited to spin up a different VM because the first has been shutdown on the main host or the host is down...
As you can see I'm still pretty new to this, thanks for any pointer.
I use pve to virtualize my opnSense router, I'm about to install and configure a second machine with another pve and another virtual router that will use CARP to do failover of the first virtual router.
I feel there is no need for me to use pve cluster features, especially since both virtual router should be 2 distinct VM running each on a distinct pve host.
No other VM should be automatically migrated from one pve host to the other when it fails...
Actually, I have one CT that is running traefik for me and is my loadbalancer/proxy to answer sollicitation from WAN clients, this CT would benefit from keeping running.
But in fact, this CT cannot be the same on both pve hosts since the failover host is much lower power/RAM.
So what I should really do is to have another CT running a smaller version of traefik on my failover pve, and spin this up when the main pve is down, just to keep some proxying working but not the full extent of what my traefik/docker CT is doing on my main pve.
I'm not sure having a pve cluster is really necessary especially since I have no physical fencing and I would turn to a raspberry pi to be the service to achieve corum.
I tend towards setting up a VIP for my traefik host and keep both the main and the failover CT running all the time.
Would welcome any advice on why I should be using pve clustering.
I see the raspberry qdevice as the main advantage, but I'm not sure that a pve cluster is well suited to spin up a different VM because the first has been shutdown on the main host or the host is down...
As you can see I'm still pretty new to this, thanks for any pointer.