Open Stack

Youcef,

Please find comments and questions below:

   1. Last Tuesday we discussed where to put 'lb_method' attribute and
   decided to keep it in both VIP and Pool and implement inheritance. Well..
   from fresh view this looks confusing, There will be some users who will
   operate with lb_method via VIP and others - via Pool, and sooner or later
   one type will take over other. The inheritance could be useful if we had >1
   pools, but we've decided to put this out of core scope. For case of
   multiple pools it would be more appropriate to call attribute 'selector' or
   'rule', just like in F5.
   2. How to retrieve error details for async calls? May we add an
   attribute 'error_details' to all objects and fill it in case of error?
   3. For DELETE requests if no body is returned then HTTP code should be
   204 "No Content". As an alternative way we may want to return object that
   is scheduled for deletion with status=PENDING_DELETE and HTTP code 202.
   4. We introduced operations to retrieve list of supported protocols and
   LB methods. Besides these there are two more that are driver-dependent:
   health monitoring and session persistence. I suppose we need to add
   operations for them too.
   5. In Remove a Pool operation there's a note: "Attempting to remove a
   pool that is used in a VIP will result in a badRequest (400) error. First
   remove the pool from the VIP, then you can destroy the pool and its
   members." Since VIP.pool_id is now scalar value would it be more correct to
   require removal of the whole VIP object before removing Pool?
   6. Let's add a note that all update operations adopt patch semantics
   (like Quantum does)
   7. Normal Response Code for 'List VIPs' and 'Retrieve VIP details'
   should be 200 (not 202)
   8. In 'Delete Health Monitor' operation the title for example should
   be "Delete a TCP Monitor" (not Update)

Thanks for great job on putting this together! We are ready to start the
implementation.

Ilya.


2012/10/27 Youcef Laribi <Youcef.Laribi at eu.citrix.com>

> I have put a first draft of the LBaaS API on the wiki page
> http://wiki.openstack.org/Quantum/LBaaS/API_1.0, so please have a look
> before next week’s meeting. There is still some work to be done on it, but
> the essential details to start the implementation should be there.****
>
> ** **
>
> Thanks,****
>
> Youcef
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121029/b558d12f/attachment-0001.html>