<div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Apr 22, 2012 at 9:57 PM, Matt Joyce <span dir="ltr"><<a href="mailto:matt@nycresistor.com" target="_blank">matt@nycresistor.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Correct me if I am wrong but mongo has not been used in openstack<br>
previously? What is the benefit here that justifies bringing in new<br>
technology?<br></blockquote><div> </div><div>Mongo is document oriented, which i consider fits perfectly with the needs. </div><div><br></div><div>It allows to query a huge json documents set.</div><div><br></div><div>In older version of OpenStack the NoSQL used was Redis, this is key oriented</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Also are you planning an active polling process over AMPQ or passive<br>
listening for the monitor?<br></blockquote><div><br></div><div>Listen: The Message Listener will feed MongoDB</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
It seems to me that most of the main components today can provide<br>
billing data via their API, </blockquote><div><br></div><div><div>You are right, the mediation has to transform the OpenStack specific data to</div><div>the billing priovider. Then using the billing provider API we can feed it.</div>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">there's no need to write anything new.<br></blockquote><div><br></div><div>We need to provider a driver for each billing provider</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Maybe we should just standardize billing related API queries across<br>
the board?<br></blockquote><div><br></div><div>I see this option outbound of OpenStack project (actually, this a rougth estimation ;)</div><div><br></div><div>Cheers!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span><font color="#888888"><br>
-Matt<br>
</font></span><div><div><br>
On Sun, Apr 22, 2012 at 12:36 PM, Luis Gervaso <<a href="mailto:luis@woorea.es" target="_blank">luis@woorea.es</a>> wrote:<br>
> Dough is the proposed billing platform/product (where the billing rules<br>
> live), isn't it?<br>
><br>
> I don't know Dough enough, so please me correct me if i'm wrong.<br>
><br>
> I'm trying to define a generic/agnostic integration process, obviously where<br>
> Dough<br>
> can fit perfectly. I would like it become part to the reference<br>
> architecture.<br>
><br>
> Option 1) [3b in the arch proposed]<br>
><br>
> Dough should pull NoSQL<br>
><br>
> Option 2)<br>
><br>
> A Mediator can feed Dough<br>
><br>
><br>
> On Sun, Apr 22, 2012 at 9:13 PM, Endre Karlson <<a href="mailto:endre.karlson@gmail.com" target="_blank">endre.karlson@gmail.com</a>><br>
> wrote:<br>
>><br>
>> What about using the Dough project?<br>
>><br>
>> Endre.<br>
>><br>
>><br>
>> 2012/4/22 Endre Karlson <<a href="mailto:endre.karlson@gmail.com" target="_blank">endre.karlson@gmail.com</a>><br>
>>><br>
>>> What about using the Dough project ?<br>
>>><br>
>>> Endre.<br>
>>><br>
>>> 2012/4/22 Luis Gervaso <<a href="mailto:luis@woorea.es" target="_blank">luis@woorea.es</a>><br>
>>>><br>
>>>> Hi,<br>
>>>><br>
>>>> I want to share the architecture i am developing in order to perform the<br>
>>>> monitorig / billing OpenStack support:<br>
>>>><br>
>>>> 1. AMQP Client which listen to RabbitMQ / QPid (this should be<br>
>>>> interchangeable) (Own Stuff or ServiceMix / Camel)<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>
>>>> 3a. The monitoring system can pull/push MongoDB<br>
>>>><br>
>>>> 3b. The billing system can pull to create invoices<br>
>>>><br>
>>>> 4. A mediation EIP should be necessary to integrate a billing/monitoring<br>
>>>> product. (ServiceMix / Camel)<br>
>>>><br>
>>>> This is to receive your feedback. So please, critics are welcome!<br>
>>>><br>
>>>> Cheers!<br>
>>>><br>
>>>> --<br>
>>>> -------------------------------------------<br>
>>>> Luis Alberto Gervaso Martin<br>
>>>> 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@woorea.es" target="_blank">luis@woorea.es</a><br>
>>>><br>
>>>><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>
>>>> 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>
>>><br>
>><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>
>> 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>
><br>
><br>
><br>
> --<br>
> -------------------------------------------<br>
> Luis Alberto Gervaso Martin<br>
> 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@woorea.es" target="_blank">luis@woorea.es</a><br>
><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>
> 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>
</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>