← Back to team overview

openstack team mailing list archive

Re: [Metering] schema and counter definitions

 

On 05/09/2012 11:11 PM, Doug Hellmann wrote:
>
>
> On Wed, May 9, 2012 at 3:07 PM, Tomasz Paszkowski <ss7pro@xxxxxxxxx <mailto:ss7pro@xxxxxxxxx>> wrote:
>
>     On Wed, May 9, 2012 at 8:02 PM, Doug Hellmann
>     <doug.hellmann@xxxxxxxxxxxxx <mailto:doug.hellmann@xxxxxxxxxxxxx>> wrote:
>     >
>     > Nice!
>     >
>     > For production code I think we are going to want to separate collection from
>     > storage, aren't we? We don't want each compute node to require access to the
>     > database server (that's an issue with nova that they are trying to fix
>     > during the folsom release, IIRC).
>
>     Yes. Part of the code responsible for amqp support is not functional yet :(
>
>
> OK, that's what I thought.
>
> We all seem to be reinventing different parts of the services that we will eventually need, which is good for education but may be wasting a bit of energy. Is it premature to start talking a little more about architecture so we can start splitting up the implementation work and focusing that energy differently? There is a lot of work we can do independently of the remaining decisions outlined in http://wiki.openstack.org/Meetings/MeteringAgenda.
Hi,

It looks like the architecture of metering is indeed always implemented in similar ways. I had discussions with a company yesterday about their own metering implementation (which will be used in production soon) and it also has an architecture matching what has been proposed so far in ceilometer. I added a few points to the architecture chapter in the wiki:

http://wiki.openstack.org/EfficientMetering#Architecture

including a note summarizing the conclusions of the discussion regarding need for an independent ceilometer agent in addition to the existing meters provided by the OpenStack components.

What do you think ?
>  
>
>
>
>
>     --
>     Tomasz Paszkowski
>     SS7, Asterisk, SAN, Datacenter, Cloud Computing
>     +48500166299 <tel:%2B48500166299>
>
>     _______________________________________________
>     Mailing list: https://launchpad.net/~openstack <https://launchpad.net/%7Eopenstack>
>     Post to     : openstack@xxxxxxxxxxxxxxxxxxx <mailto:openstack@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~openstack <https://launchpad.net/%7Eopenstack>
>     More help   : https://help.launchpad.net/ListHelp
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp


-- 
Loïc Dachary         Chief Research Officer
// eNovance labs   http://labs.enovance.com
// ? loic@xxxxxxxxxxxx  ? +33 1 49 70 99 82


References