On Thu, 27 Mar 2014 16:47:15 +0100 basti <black.flederm...@arcor.de> wrote:
> perhaps that's a bit off topic here but can someone explain what I > need to build a hardware failover nginx cluster? I a nutshell: * (at least) two Servers * a monitoring software * a shared IP * something that will switch the shared IP in case of failures One way is to use Corosync and Pacemaker. They will bring so called Ressource Agents who are capable of monitoring your nginx-Daemon and your network connection. If the daemon fails, or your network connections seems to be shaky (or gone) the Shared-IP (Service-IP) will be transfered from one Server to the other. Before that all needed services will be started if they wasn't running before. So take a look at Corosync/Pacemaker. As you seem to be German, maybe this article I wrote will help you: https://www.21x9.org/neuer-server-pacemaker-corosync-und-salt-stack/ It describes the installation of Corosync/Pacemaker using Saltstack (a configuration management tool). Leaving Saltstack aside it might give you a good overview about Corosync. Bye for now.
signature.asc
Description: PGP signature
