<div class="gmail_extra">Nick, I want contribute in the discussion group.</div><div class="gmail_extra"><br></div><div class="gmail_extra">I have seen yagi implementation, and i like it. I like the protocol.</div><div class="gmail_extra">
<br></div><div class="gmail_extra">But I think that it's a protocol that fits very well when no sensible data is involved (content feeds). When money, resources, companies are involved i think we need to use a more elaborated schema.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">I don't like the 3rd parties have to pull, my proporsal here is that 3rd parties can be entities externalized outside of the datacenter.</div><div class="gmail_extra">
<br></div><div class="gmail_extra">1. i don't want to make the accounting public accessible for security reasons.</div><div class="gmail_extra">2. 3rd parties can't be coupled to openstack, i want to feed them. I think this is the key.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">What i realized is that the listener needs to feed the billing system following the rules/api of the selected billing system.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Scenario:</div><div class="gmail_extra"><br></div><div class="gmail_extra">1. A company has an account on a billing provider</div><div class="gmail_extra">
2. A company should define the pricing model in the billing system, outside openstack (i.e: inside zuora, jbilling, recurly, dough)</div><div class="gmail_extra">3. When a message arrives to the listener the listener has to perform the following actions:</div>
<div class="gmail_extra">
<br></div><div class="gmail_extra">3a: transform and store the message in a accounting system (restful api)</div><div class="gmail_extra">3b (optional): transform and store the message in a billing system (restful api) example: [<a href="http://knowledgecenter.zuora.com/C_Zuora_User_Guides/A_Billing_and_Payments/A_Z-Billing" target="_blank">http://knowledgecenter.zuora.com/C_Zuora_User_Guides/A_Billing_and_Payments/A_Z-Billing</a>]</div>
<div class="gmail_extra">3c (optional): perform monitoring (currently evaluating sigar functionality)</div><div class="gmail_extra"><br></div><div class="gmail_extra">3a: is openstack related</div><div class="gmail_extra">
<br></div><div class="gmail_extra">3b, 3c, ...: are hooks</div><div class="gmail_extra"><br></div><div class="gmail_extra">4a. A company can query the billing system to gather the bills (no openstack dependencies)</div><div class="gmail_extra">
4b. A company can query the monitoring system (no openstack dependencies)</div><div class="gmail_extra"><br></div><div class="gmail_extra">Regarding MongoDB, I recommend a document oriented database where we can query with criteria. Redis is key-value oriented.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Cheers!<br><br><div class="gmail_quote">On Mon, Apr 23, 2012 at 4:51 PM, Kevin L. Mitchell <span dir="ltr"><<a href="mailto:kevin.mitchell@rackspace.com" target="_blank">kevin.mitchell@rackspace.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Sun, 2012-04-22 at 20:50 +0200, Luis Gervaso wrote:<br>
> I want to share the architecture i am developing in order to perform<br>
> the monitorig / billing OpenStack support:<br>
><br>
><br>
> 1. AMQP Client which listen to RabbitMQ / QPid (this should be<br>
> interchangeable) (Own Stuff or ServiceMix / Camel)<br>
><br>
><br>
> 2. Events should be stored on a NoSQL document oriented database (I<br>
> think mongodb is perfect, since we can query in a super easy fashion)<br>
<br>
</div>Except for the use of MongoDB, the above seems to me to be almost<br>
identical to the notifications system already in Nova, which Yagi<br>
consumes. Have you looked at our existing notifications? Yagi? One or<br>
both might solve at least parts of your problem…<br>
<span><font color="#888888"><br>
--<br>
Kevin L. Mitchell <<a href="mailto:kevin.mitchell@rackspace.com" target="_blank">kevin.mitchell@rackspace.com</a>><br>
</font></span><div><br>
<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>
</div><div><div>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>
</div></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: <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>
</div>