DVR: Agent side change for live migration with floatingip
During live migration when an instance is in a pre-migration
state, and if the fixed_ip of the port has an associated
floatingip, the floatingip namespace should be created in
the destination node, before the VM instance lands on the
node.
The server side code will handle the pre-live migration case
and initiate the router creation on the destination node and
also will provide the 'dest_host' as an additional attribute to
the floatingips dictionary that is being passed to the agent.
So this patch reads the 'dest_host' and the 'host' variable
and if any of the two matches with the host, it will allow
the floatingip to be processed.
This will be an agent side change for addressing the vm
migration with Floatingip enabled.
Reviewed: https:/ /review. openstack. org/260738 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=c04587110fe f24c189d439bacb bbc7105085cbe1
Committed: https:/
Submitter: Jenkins
Branch: master
commit c04587110fef24c 189d439bacbbbc7 105085cbe1
Author: Swaminathan Vasudevan <email address hidden>
Date: Tue Dec 22 13:40:33 2015 -0800
DVR: Agent side change for live migration with floatingip
During live migration when an instance is in a pre-migration
state, and if the fixed_ip of the port has an associated
floatingip, the floatingip namespace should be created in
the destination node, before the VM instance lands on the
node.
The server side code will handle the pre-live migration case
and initiate the router creation on the destination node and
also will provide the 'dest_host' as an additional attribute to
the floatingips dictionary that is being passed to the agent.
So this patch reads the 'dest_host' and the 'host' variable
and if any of the two matches with the host, it will allow
the floatingip to be processed.
This will be an agent side change for addressing the vm
migration with Floatingip enabled.
Closes-Bug: #1456073 1df5d3050912d62 0591c69b614
Change-Id: Idfbea7f3c66d6a