Open Stack

On 01/30/2013 09:32 AM, Julien Danjou wrote:
> On Tue, Jan 29 2013, Angus Salkeld wrote:
> 
>> Nice walk through, I need to try digest how that is all going to fit together.
>>
>> It initially seems to me that there is a new entity "Notification/TracePoint"?
>> They don't really seem like meters, and it might make sense to just model
>> correctly rather than trying to squeeze them into meters.
> 
> +1
> 
> From what I understand from your video, StackTach logs raw notifications
> and then feed data into a few tables, doing some computing.
> 
> So what it does is down to:
> 1. Stock raw notifications
> 2. Compute values from these notifications and cache them (= store them
>    into a few tables)
>    Some of these values might be meters.
> 
> I don't think Ceilometer collector is going to store raw notifications.
> There's no point into the whole Ceilometer project to store this data.

Perhaps in your deployment, we have downstream clients that are
definitely going to want access to the rich information. We may be able
to pare that down to a smaller subset, but right now we have no idea
what they're going to want.

> Your best call here is probably to keep that part of StackTach if you
> really need all the raw notifications.

Well, that's not our goal here. We don't want to maintain two
applications for archiving.


> For things are likely to be meter (i.e. things with a duration and/or a
> volume), you can write some Ceilometer notification plugin building a
> bunch of meter from what you get. Multi-publisher can also help you
> building more advanced counter through the use of transformer if you
> wish.

Do you mean a nova compute notification plugin?

That's the sort of thing we want to get away from, installing custom
stuff on the compute nodes.

-S

> 
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>