<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 05/10/2012 05:46 AM, Daniel Dyer wrote:
<blockquote
cite="mid:CAK3=mR_bmkiD5jwcVpX_+aJiEdD4u=qptSJTnYJWugyDHv5vmg@mail.gmail.com"
type="cite">Is it your assumption that there will be one metering
service per "installation" or one per service (i.e swift, nova)?
My assumption would be a single metering service, so the API would
need to handle some additional use cases:<br>
-list services supported<br>
-list metrics for a service type<br>
-get metric details<br>
<br>
</blockquote>
Hi,<br>
<br>
I added the "list services supported" assuming service == OpenStack
component (nova, swift etc.)<br>
<br>
<a class="moz-txt-link-freetext" href="http://wiki.openstack.org/EfficientMetering?action=diff&rev2=66&rev1=65">http://wiki.openstack.org/EfficientMetering?action=diff&rev2=66&rev1=65</a><br>
<br>
I added the "list meters for a component" <br>
<br>
<a class="moz-txt-link-freetext" href="http://wiki.openstack.org/EfficientMetering?action=diff&rev2=67&rev1=66">http://wiki.openstack.org/EfficientMetering?action=diff&rev2=67&rev1=66</a><br>
<br>
I'm not sure what you mean by "metric details", could you expand ?
It could be a description (human readable ?) of a given meter. Since
we're using a fixed form storage, I'm not sure what else needs to be
returned.<br>
<br>
Cheers<br>
<blockquote
cite="mid:CAK3=mR_bmkiD5jwcVpX_+aJiEdD4u=qptSJTnYJWugyDHv5vmg@mail.gmail.com"
type="cite">I would also consider separate use cases for accessing
raw events vs. aggregated metrics.<br>
<br>
Dan Dyer<br>
<a moz-do-not-send="true" href="mailto:dan.dyer@hp.com">dan.dyer@hp.com</a><br>
<br>
<div class="gmail_quote">On Wed, May 9, 2012 at 10:44 AM, Nick
Barcet <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:nick.barcet@canonical.com" target="_blank">nick.barcet@canonical.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
<br>
Doug Hellmann <<a moz-do-not-send="true"
href="mailto:doug.hellmann@dreamhost.com">doug.hellmann@dreamhost.com</a>>
wrote:<br>
<br>
>On Wed, May 9, 2012 at 11:27 AM, Nick Barcet<br>
><<a moz-do-not-send="true"
href="mailto:nick.barcet@canonical.com">nick.barcet@canonical.com</a>>wrote:<br>
><br>
>> On 05/08/2012 08:27 AM, Nick Barcet wrote:<br>
>> [..]<br>
>><br>
>> Thinking about this, I think we need to expend the
API a bit to<br>
>reflect<br>
>> the evolutions of the schema that we decided last
week. Here are my<br>
>> proposals:<br>
>><br>
>> > * Requests allow to<br>
>> > GET account_id list<br>
>><br>
>> change to: GET [user_id|project_id|source] list<br>
>><br>
><br>
>Does the [value|value] syntax mean "choose one" or
"combine"? I assume<br>
>"choose one" and you are using square brackets because
parens are used<br>
>in some of the other queries.<br>
<br>
</div>
You assumed correctly :)<br>
<div class="im"><br>
>><br>
>> > GET list of counter_type<br>
>> > GET list of events per account<br>
>> > optional start and end for
counter_datetime<br>
>> > optional counter_type<br>
>><br>
>> change to: GET list of events per
[user_id|project_id|source]<br>
>> optional start and end for counter_datetime<br>
>> optional counter_type<br>
>><br>
><br>
>Users may cross projects, so I'm not sure it makes sense
to ask for the<br>
>events generated by a user without restricting it by the
project. At<br>
>the very least we may need to allow them to specify
user_id or project_id<br>
>or both.<br>
<br>
</div>
Good point. Thanks for catching this.<br>
<div class="HOEnZb">
<div class="h5"><br>
>><br>
>> > GET sum of (counter_volume,
counter_duration) for counter_type<br>
>and<br>
>> > account_id<br>
>> > optional start and end for
counter_datetime<br>
>><br>
>> GET sum of (counter_volume, counter_duration)
for counter_type and<br>
>> [user_id|project_id|source]<br>
>> optional start and end for counter_datetime<br>
>><br>
>> Hope this makes sense.<br>
>><br>
>> Another item that we need to discuss is
extensibility of this API.<br>
>><br>
>> Nick<br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack"
target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a moz-do-not-send="true"
href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a moz-do-not-send="true"
href="https://launchpad.net/%7Eopenstack"
target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a moz-do-not-send="true"
href="https://help.launchpad.net/ListHelp"
target="_blank">https://help.launchpad.net/ListHelp</a><br>
</div>
</div>
</blockquote>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
Post to : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
More help : <a class="moz-txt-link-freetext" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="3000">--
Loïc Dachary Chief Research Officer
// eNovance labs <a class="moz-txt-link-freetext" href="http://labs.enovance.com">http://labs.enovance.com</a>
// ✉ <a class="moz-txt-link-abbreviated" href="mailto:loic@enovance.com">loic@enovance.com</a> ☎ +33 1 49 70 99 82
</pre>
</body>
</html>