Open Stack

On 01/30/2013 10:39 AM, Julien Danjou wrote:
> On Wed, Jan 30 2013, Sandy Walsh wrote:
> 
>> I don't understand the difference? Metering assumes archiving. If any
>> company with SEC requirements wants to use Ceilometer for billing, for
>> example, they'll have to store 90+ days of data.
>>
>> Can you elaborate on the ceilometer mandate?
> 
> Notifications aren't all about metering. Actually, they are called
> "notifications", not "meters". Things would be different if
> Nova/Glance/etc would emit directly meters, for example (hint hint).
> 
> Remember that Ceilometer is also providing an API endpoint to be
> queried, and what it stores via its `collector' is directly made to be
> used via its API.
> So the essence of the collector service is to treat and transform
> notifications into meters. To do metering.
> 
> Now, if what you want is to archive all notifications and build meters
> From that, there's a couple of solution, based on and around Ceilometer,
> but I don't think Ceilometer is going to be enough.
> 
> For example, you could have a smaller project just listening to
> notifications and storing them in a databse like StackTach does, and
> move the metering part into Ceilometer.
> Or you could write a driver notifier storing directly the notification
> into a database actually, I guess that depends on what you want to
> achieve.
> 
> But Ceilometer itself has no use of the raw notificatins once it has
> transformed them into meters.

Interesting ... it this the final say on this matter?





>> Sorry, I still trip over the ceilometer terminology. I was citing your
>> comment above about "Ceilometer notification plugin" ... and the only
>> one I was aware of was the one here:
>> https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/nova_notifier.py
>>
>> And, if so, I was saying that's the thing we don't really need.
> 
> Ah right, I get it. No, I was talking about plugin.NotificationBase,
> which is the way you can handle notifications coming from Nova (or other
> OpenStack components) in Ceilometer.
> You can write a plugin using that (that will be used by
> ceilometer-collector) to listen to (all) notifications and build any
> meter. And even more complicated meter with transformers.
> 

Thanks, and sorry for the confusion (still getting my feet here). I'll
look at that code and try to understand how it differs from the exist
Agent model.

-S