Ha fip: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
== High Availability using a floating IP == | == High Availability using a floating IP == | ||
A single VM hosting an application can fail and be offline, which makes the application inaccessible | A single VM hosting an application can fail and be offline, which also makes the application inaccessible. | ||
To avoid a scenario | 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: | |||
1. 2 VMs hosting the application | |||
2. 1 Floating IP | |||
3. 1 VIP (shared IP) RFC1918 from within your project | |||
Revision as of 15:26, 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:
1. 2 VMs hosting the application 2. 1 Floating IP 3. 1 VIP (shared IP) RFC1918 from within your project