I just upload a video that shows the way i manage the billing described in my previous mail in order to clarify:<div><br></div><div><a href="http://youtu.be/3A1SdZS9Iak">http://youtu.be/3A1SdZS9Iak</a><br><div><br></div><div>
Data is gathered and correlated in a own metering agent that i want to conform with the ceilometer spec.</div><div>Data is submited to the billing system.</div><div><br></div><div>The billing process then can be run on demand or scheduled.</div>
<div><br></div><div>Regards</div><div><br></div><div><br><div class="gmail_quote">On Thu, May 3, 2012 at 3:01 AM, Luis Gervaso <span dir="ltr"><<a href="mailto:luis@woorea.es" target="_blank">luis@woorea.es</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Agree with your comments,<div><br></div><div>1. Metering tasks for me are mainly 2:</div><div><br></div><div>a) Collect relevant data</div>
<div>b) Correlate events (that's which "end event" corresponds with which "event start") this is very important, </div>
<div>since only openstack knows how to correlate, but the billing system</div><div><br></div><div><div>2. Mediation process should exist, one per billing system (a.k.a driver, openstack-specific-billing-system-plugin)</div>
<div><br></div><div>Map previously correlated data to a pricing model</div></div><div><br></div><div>3. Billing system tasks (obviously outscope openstack, it's does know nothing about cloud)</div><div><br></div><div>
Regards</div><div><br></div><div><div><div class="h5"><br><div class="gmail_quote">On Thu, May 3, 2012 at 12:10 AM, Doug Hellmann <span dir="ltr"><<a href="mailto:doug.hellmann@dreamhost.com" target="_blank">doug.hellmann@dreamhost.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="gmail_extra"><br><br><div class="gmail_quote"><div>On Wed, May 2, 2012 at 2:31 PM, Joshua Harlow <span dir="ltr"><<a href="mailto:harlowja@yahoo-inc.com" target="_blank">harlowja@yahoo-inc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">Hi all,<br>
<br>
I was just looking over the efficient metering stuff yesterday.<br>
<br>
Just a couple of questions, that might be dups (sorry if they are).<br>
<br>
I am noticing that there seems to be a mix of billing specifics there and metering specifics there.<br>
<br>
If say metering can just provide as much raw data as possible then is that not sufficient? Shouldn’t that be the limit of openstack’s job?<br></span></font></div></blockquote><div><br></div></div><div>I believe the rest of the group is reaching that conclusion, too. There was some discussion of that in the recent "schema and counter definitions" thread.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">
<br>
Then there can be sets of business units or other people that figure out how to carve up that raw data into billing equivalents. This is especially since every business will have there own idears around billing. In certain situations, I can even think where one would want to use hadoop to calculate some advanced model of all that raw-data and use that for billing, but the key part that keeps on coming up in my brain is just get as much raw data as possible.<br>
<br>
Thoughts??<br>
<br>
-Josh<br>
<br>
</span></font>
</div>
<br></div>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net" target="_blank">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br>-------------------------------------------<br>Luis Alberto Gervaso Martin<div>Woorea Solutions, S.L<br>
CEO & CTO<br>mobile: <a href="tel:%28%2B34%29%20627983344" value="+34627983344" target="_blank">(+34) 627983344</a><br><a href="mailto:luis.gervaso@gmail.com" target="_blank">luis@</a><a href="http://woorea.es/" target="_blank">woorea.es</a></div>
<br>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>-------------------------------------------<br>Luis Alberto Gervaso Martin<div>Woorea Solutions, S.L<br>CEO & CTO<br>mobile: (+34) 627983344<br><a href="mailto:luis.gervaso@gmail.com" target="_blank">luis@</a><a href="http://woorea.es/" target="_blank">woorea.es</a></div>
<br>
</div></div>