Separate nat and eip failover functionality #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background:
The nat instances have dual functionality. It serves as a gateway for entercard auths and hence has to be configured to associate with itself elastic ips (eip). It also functions as a nat for the instances in the private zone.
Because of this, it handles failovers for nat and eip when any of the nats goes down. If the eip failover breaks, it will not be assigned a public ip and hence the instance won't have access to the internet. Because of this, the nat functionality would also break. When this happens, the impact is that we won't receive entercard auths and also the instances connected to the failed zones will be down and eventually services in these zones will also go down.
Solution:
Separate eip and nat "failover" functionality. Execute re-route related functionality only on nat clusters and eip related functionality only on eip clusters.
References https://github.com/wrapp/whaleshark/pull/55