Open Stack

Hi Pattabi,

There is no any specific reason of it this other than it was a quick
solution made for the reference implementation.
We planned to revisit this in Havana because clearly quantum port may be
used for several VIPs.
However it might be not that simple because the actual change that is
needed is a pool having several VIPs. Currently it is 1:1 mapping.

Thanks,
Eugene.

On Sat, Jun 15, 2013 at 6:50 AM, Pattabi Ayyasami <pattabi at brocade.com>wrote:

> Hi All,****
>
> ** **
>
> In quantum/db/loadbalancer_db.py, for every Vip creation, I see that a
> Quantum Port is also created (using the core quantum plugin). ****
>
> This basically limits us from creating multiple Vip Ports ( For example,
> for a virtual ip  say, 10.1.1.5, creating an HTTP Port and another Custom
> Port or DNS Port etc) as the code checks for IpAddress Uniqueness and fails
> with IpAddressInUse Error. ****
>
> ** **
>
> I would like to understand the reason/logic of this implementation. Our
> hardware load balancers allow the end user to create multiple ports for a
> given virtual IP and wondering to support that via Open Stack.  ****
>
> ** **
>
> Your response on this is highly appreciated.****
>
> ** **
>
> Regards,****
>
> Pattabi ****
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130615/2e1dd9b2/attachment.html>