Some questions about floating ip migration which I think are worth discussing within neutron team before starting a cross-project discussion on this:
- what is the right time for a floating ip to be created on destination host, if there is any for DVR scenario?
- on pre migration step Floating IP should be active on the source host where VM is still located, so we can't prepare everything on destination host on pre migration (even if nova would wait for it). Or can we?
- can we have same Floating IP on two nodes at the same time and what are side effects?
- if we can will it (how will it) help to not loose ssh connection during live migration?
- if we can't what is the right moment for floating ip transition?
- if we have a notification from nova to neutron at the right moment (when VM is actually "migrating" to the destination) will it still be enough to preserve ssh connection? (in this case neutron server should notify l3 agent and agent needs to process the router, which currently means going back to server for router info)
Some questions about floating ip migration which I think are worth discussing within neutron team before starting a cross-project discussion on this:
- what is the right time for a floating ip to be created on destination host, if there is any for DVR scenario?
- on pre migration step Floating IP should be active on the source host where VM is still located, so we can't prepare everything on destination host on pre migration (even if nova would wait for it). Or can we?
- can we have same Floating IP on two nodes at the same time and what are side effects?
- if we can will it (how will it) help to not loose ssh connection during live migration?
- if we can't what is the right moment for floating ip transition?
- if we have a notification from nova to neutron at the right moment (when VM is actually "migrating" to the destination) will it still be enough to preserve ssh connection? (in this case neutron server should notify l3 agent and agent needs to process the router, which currently means going back to server for router info)