Hi, Although metering and billing always comes together for the deployment, for the sake of clarity, I also think metering should be a separate project from the billing, especially in openstack. (As you mentioned it, billing is complex and has too many different requirements per provider)
Anyway, I am really interested in weekly meeting you mentioned in the email. How can I join the meeting? Is it irc-meeting?, mailing-list?, or else? -- Jaesuk Ahn, Ph.D. Team Leader | Cloud OS Dev. Team Cloud Infrastructure Department KT (Korea Telecom) T. +82-10-9888-0328 | F. +82-303-0993-5340 Active member on OpenStack Korea Community Apr 23, 2012, 4:09 PM, Nick Barcet 작성: > Hello Luis, > > I presented a blueprint last week [1] which proposes to clearly > differentiate metering from the overall billing process. It is my > understanding that billing is too complex a beast to be solved for each > requirement in a satisfactory way and have therefore proposed that we > should first concentrate on collecting the informations necessary for > billing systems to pull their information from. > > The blueprint, and the discussion we had at the summit last week, > outlines a proposed architecture but has, so far, left open the > component choices to implement it. It is our proposal to start a a > weekly meeting from that week to start selecting the components to > deliver this. You are more than welcome to join the project if you want. > > [1] http://wiki.openstack.org/EfficientMetering > > Best regards, > Nick > > On 04/22/2012 08:50 PM, Luis Gervaso wrote: >> Hi, >> >> I want to share the architecture i am developing in order to perform the >> monitorig / billing OpenStack support: >> >> 1. AMQP Client which listen to RabbitMQ / QPid (this should be >> interchangeable) (Own Stuff or ServiceMix / Camel) >> >> 2. Events should be stored on a NoSQL document oriented database (I >> think mongodb is perfect, since we can query in a super easy fashion) >> >> 3a. The monitoring system can pull/push MongoDB >> >> 3b. The billing system can pull to create invoices >> >> 4. A mediation EIP should be necessary to integrate a billing/monitoring >> product. (ServiceMix / Camel) >> >> This is to receive your feedback. So please, critics are welcome! >> >> Cheers! >> >> -- >> ------------------------------------------- >> Luis Alberto Gervaso Martin >> Woorea Solutions, S.L >> CEO & CTO >> mobile: (+34) 627983344 >> luis@ <mailto:luis.gerv...@gmail.com>woorea.es <http://woorea.es/> >> >> >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp