Fix method dvr_update_router_addvm to notify every
router attached to subnet where the vm will boot
on.
In dvr case, when a subnet only attaches to one router,
the subnet will only have one distributed router interface,
which device_owner is "network:router_interface_distributed".
So in this case, get_ports in this method will only get
one port, and it should be unnecessary to break in for loop.
But when a subnet attaches multiple routers, get_ports in
this method will return all distributed router interfaces
and the routers hold those interfaces should be notified
when an instance booted on the subnet. So it should also
be unnecessary to break in for loop.
Change-Id: I3a5808e5b6e8b78abd1a5b924395844507da0764
Closes-Bug: #1427122
Co-Authored-By: Ryan Moats <email address hidden>
Reviewed: https:/ /review. openstack. org/160289 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=24fa37e0554 4316b58357b7533 60b147878e5d94
Committed: https:/
Submitter: Jenkins
Branch: master
commit 24fa37e05544316 b58357b753360b1 47878e5d94
Author: lzklibj <email address hidden>
Date: Mon Mar 2 02:13:41 2015 -0800
Fix dvr update for subnet attach multi subnets
Fix method dvr_update_ router_ addvm to notify every
router attached to subnet where the vm will boot
on.
In dvr case, when a subnet only attaches to one router, router_ interface_ distributed" .
the subnet will only have one distributed router interface,
which device_owner is "network:
So in this case, get_ports in this method will only get
one port, and it should be unnecessary to break in for loop.
But when a subnet attaches multiple routers, get_ports in
this method will return all distributed router interfaces
and the routers hold those interfaces should be notified
when an instance booted on the subnet. So it should also
be unnecessary to break in for loop.
Change-Id: I3a5808e5b6e8b7 8abd1a5b9243958 44507da0764
Closes-Bug: #1427122
Co-Authored-By: Ryan Moats <email address hidden>