commit 537f480927293755bd6365068c1abd0c80951bad
Author: Matt Riedemann <email address hidden>
Date: Wed May 17 22:48:29 2017 -0400
Handle network-changed event for a specific port
It turns out that when Neutron sends the "network-changed"
event it has a port in scope and can provide the port ID.
Older versions of Neutron wouldn't send this, but if it's
provided, we can try to optimize the network info cache
refresh and scope it to just that single port, rather than
build the entire cache all over again when the other ports
in the cache may not have changed at all since the last
time the cache was refreshed.
This can be especially beneficial for instances with a
relatively large number of ports which are being migrated.
Reviewed: https:/ /review. openstack. org/465787 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=537f4809272 93755bd6365068c 1abd0c80951bad
Committed: https:/
Submitter: Zuul
Branch: master
commit 537f48092729375 5bd6365068c1abd 0c80951bad
Author: Matt Riedemann <email address hidden>
Date: Wed May 17 22:48:29 2017 -0400
Handle network-changed event for a specific port
It turns out that when Neutron sends the "network-changed"
event it has a port in scope and can provide the port ID.
Older versions of Neutron wouldn't send this, but if it's
provided, we can try to optimize the network info cache
refresh and scope it to just that single port, rather than
build the entire cache all over again when the other ports
in the cache may not have changed at all since the last
time the cache was refreshed.
This can be especially beneficial for instances with a
relatively large number of ports which are being migrated.
Depends-On: Ifdaef05208d09d dd9587fed6214cf 388e5265ba4
Change-Id: I023b5b1ccb248e 68189f62ba0ff75 d41093c1f60
Partial-Bug: #1691602