Comment 3 for bug 1445255
Revision history for this message
| Swaminathan Vasudevan (swaminathan-vasudevan) wrote Re: DVR FloatingIP to unbound port does not work | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Allowed address pair by itself is not tied to the DVR or floatingIP.
With DVR floatingIP traffic in/out is through the compute Node. So basically we create routers and assign floatingIP based on the port binding and as well as the "device_owner" of the port.
In order to support this scenario, either we need to manually set the "device_owner" for the port if intended to use with the FloatingIP on a DVR router. Once the "device_owner" is set, it has to be updated to the list of "DVR" serviceable ports.
Because today we do have a list of "DVR serviceable ports" such as "compute, lbaas-vip and dhcp". We might need to add this special port to that list in order for DVR to honor it.
Also this port should be binded to a host, so that we know where to deploy our FloatingIP namespace.
This is all happening because of the dynamic nature of the DVR in creating and deleting the FIP Namesapces.