Open Stack

Hi Oleg,

Yes you are right, you can achieve these 2 calls through using query string parameters, but I felt these calls are so common, that it's worth dedicating API calls for these. One often wants to know the members of a pool or the health monitors attached to the pool, and using the form of sub-resource URL looks more natural and obvious.

Thanks
Youcef

From: Oleg Bondarev [mailto:obondarev at mirantis.com]
Sent: Monday, November 12, 2012 6:41 AM
To: Youcef Laribi; 'OpenStack Development Mailing List'
Subject: [openstack-dev][quantum][LBaaS] yet another question on API

Hi Youcef,

IMHO  the following API (http://wiki.openstack.org/Quantum/LBaaS/API_1.0) operations are redundant:

1)      List all members of a specific pool
GET

/v1.0/pools/pool_id/members

List all members of a specific pool.


2)      List Health Monitors associated with a pool
GET

/v1.0/pools/pool_id/health_monitors

List Health Monitors associated with a pool.

as it can be done using filtering and column selection (http://docs.openstack.org/api/openstack-network/2.0/content/filtering.html), like this

1)      /v1.0/members/?pool_id=pool_id

2)      /v1.0/pools/pool_id?fields=health_monitors

What do you think?

Thanks,
Oleg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121112/62048460/attachment.html>