One thing that annoys me is if you are logged in to host A and shut it down, you then have to open a new session manually on the other host (my use case is a 2-host cluster with qdevice). I'm wondering if it's crazy to use keepalived to implement a virtual IP for the cluster? I know it won't be 100% seamless, but might be less of a nuisance if the logged-in node goes away? I'm already doing this for 2 dnsmasq instances.
Virtual IP for GUI?
- Thread starter dswartz
- Start date
You could also create multiple DNS-Records with the same name (cluster.example.com = IP: Node01, IP: Node02, ...).
It's not as seamless as a load balancer, but for small Clusters it's well enough. But keep in mind, this approach relies on the ability of your browser to use another IP if it can't connect.
It's not as seamless as a load balancer, but for small Clusters it's well enough. But keep in mind, this approach relies on the ability of your browser to use another IP if it can't connect.
Last edited: