Ha fip: Difference between revisions
Jump to navigation
Jump to search
| Line 11: | Line 11: | ||
# 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 | |||
Assuming your application is already running on the 2 webservers, we will now allocate a 3rd IP used as VIP, which is then used by the active VM. | |||
Revision as of 15:48, 27 June 2024
This article is a draft
This is not a complete article: This is a draft, a work in progress that is intended to be published into an article, which may or may not be ready for inclusion in the main wiki. It should not necessarily be considered factual or authoritative.
High Availability using a floating IP
A single VM hosting an application can fail and be offline, which also makes the application inaccessible.
To avoid such a scenario, it is possible to make the floating IP (FIP) high-available, which in turn can be used to make the application high available too.
Active-Passive High-availability
To accomplish a setup like this, we need the following:
- 2 VMs hosting the application
- 1 VIP (shared IP) RFC1918 from within your project
- 1 HA Floating IP
Assuming your application is already running on the 2 webservers, we will now allocate a 3rd IP used as VIP, which is then used by the active VM.