Skip to content
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

Gateway high availability (Plan B) #112

Open
changbl opened this issue Jul 23, 2014 · 0 comments
Open

Gateway high availability (Plan B) #112

changbl opened this issue Jul 23, 2014 · 0 comments
Assignees
@changbl
Milestone
Release 0.1

Comments

@changbl
Copy link

changbl commented Jul 23, 2014

Long term solution is Plan B (only public VIP, and controller reschedules inter-datacenter and Internet flows upon gateway failure to a living gateway)
Problems with Plan A (master + backup gateways via Keepalived for both private and public VIPs)
(1) Break the assumption of 1-to-1 mappings between switch "IP" and "DPID", since master and backup gateways share a same VIP. Make it hard and tricky to implement.
(2) VMAC generation is based on switch DPID. Regular switches can only communicate with the master or the backup gateway, but not both
(3) bakcup gateway can only be started after all regular switches are connected, otherwise the forwarding flows cannot be setup since DPIDs/VMACs of regular switches are unknown to it.
@changbl changbl added this to the Release 0.1 milestone Jul 23, 2014
@changbl changbl self-assigned this Jul 23, 2014
@changbl changbl modified the milestone: Release 0.1 Jul 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@changbl changbl

Labels
None yet
Projects
None yet
Milestone
Release 0.1
Development

No branches or pull requests
1 participant
@changbl