Open Stack

On Tue, Aug 07 2012, Doug Hellmann wrote:

> First, when asking for values about a given resource, there isn't any
> reason to specify the user or project because they won't change for a given
> resource. I don't think it's going to be useful to ask for a complete dump
> of all of the metering data for a user at one time, since the events will
> refer to different resources and meters. That eliminates several
> variations, so instead of 16 URLs listed in the current implementation, we
> have 3:
>
> /users/<user>/<meter>
> /projects/<project>/<meter>
> /resource/<resource>/<meter>

That makes sense.

> These changes give us a two benefits. Primarily, the API is easier to use,
> since there are fewer individual calls. It will also be easier to
> implement, since we won't have so many endpoints that are really just
> alternative forms of the same query.
>
> If the rest of the team agrees, I would like to make these changes in the
> next couple of weeks as part of the work that we will be doing to integrate
> ceilometer with the billing system at DreamHost.

+1

-- 
Julien Danjou
# Free Software hacker & freelance
# http://julien.danjou.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20120807/a9babbbe/attachment-0001.pgp>