Open Stack

Hi, 

If you check the db model quantum/db/loadbalancer/loadbalancer_db.py, pool's vip_id will be updated when an VIP is created. So current work flow is correct. 

Thanks, 
-Kaiwei 

----- Original Message -----

From: "Kuang-Ching Wang" <kc.wang at bigswitch.com> 
To: "OpenStack Development Mailing List" <openstack-dev at lists.openstack.org> 
Sent: Saturday, February 2, 2013 9:09:25 PM 
Subject: [openstack-dev] [quantum] question on LBaaS API 1.0 vip/pool creation order 

Hi, 


based on the high level task flow in LBaaS API 1.0 ( http://wiki.openstack.org/Quantum/LBaaS/API_1.0 ) Chapter 1, a tenant can first create a pool and later create a VIP for the pool. 


However, currently in quantum/quantum/extensions/loadbalancer.py, pool['vip_id'] does not allow PUT, and hence once if a vip is created after a pool, the vip_id cannot be updated to a pool. 


I wonder which of the following is true: 
1. The task flow has changed since then, and expects vip to be created together at (before) pool's creation. 
Or, 
2. quantum/quantum/extensions/loadbalancer.py will be updated to allow pool['vip_id'] to be updated? 


Thanks, 
KC 






-- 
Kuang-Ching (KC) Wang 
Member of Technical Staff -- Big Switch Networks -- http://www.bigswitch.com/ 








_______________________________________________ 
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/20130202/60e886d5/attachment.html>