Ha fip: Difference between revisions

Jump to navigation Jump to search
332 bytes added ,  4 months ago
Line 27: Line 27:
==== Active-Passive High-Availability ====
==== Active-Passive High-Availability ====


Active-Passive is a setup, where one system is the active one and is being used and the passive system is the standby system,
The scenario in this document describes am ''active-passive'' system, where one system is own the VIP and receives all the network traffic for that IP address, while the other one simply stands by as backup system if the current active one fails or becomes unreachable.  
which is only used when the active system becomes unavailable.


To accomplish a setup like this, we need the following:
There are many way on how to achieve this goal and it depends on the desired outcome what needs to be done and configured.
 
The setup described below will only make sure that a system is reachable via IP, it will not take care of the availability of your application data, such a files, or it's services, such a a running webserver software.
 
This example setup will use:


# 2 VMs hosting the application
# 2 VMs hosting the application
# 1 VIP (shared IP) RFC1918 from within your project
# 1 VIP (shared IP) RFC1918 from within your project
# 1 HA Floating IP
# 1 HA Floating IP
# plan on how to access the real VMs if you don't have IPv6 connectivity


Now it's time to build the 2 VMs and install the application on both systems, this example here will only have nginx running,
Now it's time to build the 2 VMs and install the application on both systems, this example here will only have nginx running,
displaying the default index page and show that the application is reachable.
displaying the default index page and show that the application is reachable.
----


==== Installing nginx and keepalived ====
==== Installing nginx and keepalived ====
cc_staff
247

edits

Navigation menu