-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Virtual IP /HA setup using PaceMaker+Corosync does not work on AWS #7
Comments
From https://www.quora.com/How-do-I-do-custom-VIP-failover-between-EC2-instances-in-an-AWS-VPC
On AWS, this means that even though our pacemaker+corosync setup itself works perfectly to assign and float an IP from one node to another, that VIP is not visible to any other node, except the node it is setup on. We have to resort to using AWS own LB mechanisms to achieve HA. This makes it pointless to setup HA on AWS, using pacemaker and corosync. We must resort to using AWS own mechanisms to achieve HA. |
How this is supposed to be done is explained: |
Hello, I am facing the similar issue in our environment, |
I know this is an old issue, but I believe this can be solved by using the ocf_heartbeat_awsvip resource which was created to move a secondary IP around. https://www.mankier.com/7/ocf_heartbeat_awsvip |
I about one year try this issue in AWS cloud. |
On AWS, the pacemaker+corosync setup works to an end where it assigns an extra IP address to one of the HA cluster nodes , but that extra IP is not visible to any node on that subnet.
The text was updated successfully, but these errors were encountered: