Skip to content

EIP Failover II #2

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.

Sign up for GitHub

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

Jump to bottom
Open
dsouzajude wants to merge 1 commit into
base: eip-failover
Choose a base branch
from
Open

EIP Failover II #2

dsouzajude wants to merge 1 commit into from

Conversation

@dsouzajude
Copy link
Contributor

@dsouzajude dsouzajude commented Apr 14, 2015

  • Failover is based on "failing over" elastic ip on to eth1
  • Subnet routing will always go through eth0
  • On launch of instance, (specifically on the serf's member-join event) the instance will always have a single network interface eth0 and an elastic ip will be associated with it.
  • Only at the time of failover, the running instances will attach a new network interface and associate the elastic ip of the failed instance onto eth1

Dependency:
https://github.com/wrapp/whaleshark/pull/31

@dsouzajude dsouzajude changed the title only attach and use eth1 on failover EIP Failover II Apr 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@dsouzajude