DVR: Handle unbound allowed_address_pair port with FIP
If an allowed_address_pair port associated with a FloatingIP
is configured to a service_port, the allowed_address_pair port
should inherit the service_ports host binding and device
owner if device_owner is not configured.
Hence the DVR will be able to deploy the FloatingIP for
the provided allowed_address_pair.
In this case if the associated port's admin state changes,
the allowed_address_pairs device_owner and host binding will
be reverted back to None.
When associated service port is deleted the allowed_address_
pairs device_owner and host binding will be reverted as well.
Reviewed: https:/ /review. openstack. org/254439 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=6185a09d130 edb7a21e21a354b 3fa12fcbebe8a6
Committed: https:/
Submitter: Jenkins
Branch: master
commit 6185a09d130edb7 a21e21a354b3fa1 2fcbebe8a6
Author: Swaminathan Vasudevan <email address hidden>
Date: Fri Dec 4 16:44:44 2015 -0800
DVR: Handle unbound allowed_ address_ pair port with FIP
If an allowed_ address_ pair port associated with a FloatingIP address_ pair port
is configured to a service_port, the allowed_
should inherit the service_ports host binding and device
owner if device_owner is not configured.
Hence the DVR will be able to deploy the FloatingIP for address_ pair.
the provided allowed_
In this case if the associated port's admin state changes, address_ pairs device_owner and host binding will
the allowed_
be reverted back to None.
When associated service port is deleted the allowed_address_
pairs device_owner and host binding will be reverted as well.
Change-Id: I32b8d3e85a8e12 fc146c419766596 fcfb61f32f6
Closes-Bug: #1445255