Comment 5 for bug 1942329
Revision history for this message
| Balazs Gibizer (balazs-gibizer) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
We have a slight complication. There are two cases:
1) During cold migration, resize, evacuation nova directly updates the binding:host_id to rebind the port to the destination host. In this case it is OK to allow that the request changing the host_id also changes the MAC.
2) During live migration nova first creates an inactive port binding for the port on the dest, then later activates that binding. In this case there is no single request changing the port mac and the active binding:host_id. It seems that in this case the MAC address is more related to the binding objects and the port.mac_address should reflect the MAC address in the active port binding. Nova could add the MAC to the inactive binding before activating it.