[openstack-dev] [Quantum][LBaaS] vip_id in pool creation API

Youcef Laribi Youcef.Laribi at eu.citrix.com
Wed Dec 5 19:56:00 UTC 2012

Hi Leon,

The reason the spec said this is to ensure that the information in the VIP (which pool_id is used by the VIP) and the information in the pool (to which VIP the pool belongs, if it belongs to one), never get out-of-sync. If we allowed separate updates, then someone can update the pool to be associated with a new VIP, but the old VIP still thinks the pool is associated with it.


From: Leon Cui [mailto:lcui at vmware.com]
Sent: Wednesday, December 5, 2012 10:24 AM
To: Youcef Laribi
Cc: openstack-dev at lists.openstack.org
Subject: [Quantum][LBaaS] vip_id in pool creation API

Hi Youcef,
In Create_Pool API, the spec says "Optionally, you can also assign the pool to a vip during creation time, by specifying the vip_id attribute.".  I don't think we should allow user to do it because it means that it will modify the "pool_id" of a VIP in an implicitly way.  I suggest that don't allow user to provide vip_id during pool creation api. User can always to update the VIP by given a different pool_id.

What do you think?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121205/005d465c/attachment.html>

More information about the OpenStack-dev mailing list