Open Stack

Er, I'm somewhat confused at this. 

Having the audit run from the volume manager as a periodic task is good (Nova already does this), but, first, running it every 60 seconds would produce *way* too much notification traffic, 
and second removing the audit_period breaks the usage notification model. 

Cinder and Nova already produce immediate notifications (volume.create.* and volume.delete.* for Cinder, and many many types (compute.instance.create.*, etc) for Nova) 

The audit events are meant for to provide a baseline for each period,  so at any instant, you can know "the last period, there was these x volumes/instances, and I just got a create event, so now there is x+1", 
and you don't have to look back through history to the beginning of time to get an accurate count. 

I do not think this is necessary. 


On Nov 5, 2012, at 9:34 AM, Julien Danjou wrote:

> Hi,
> 
> I've been working to change the actual audit code used into Cinder (but
> also in Nova) to a real-time one, so it's more useful to projects like
> Ceilometer.
> 
> The implementation for Cinder is under review at:
> 
>    https://review.openstack.org/#/c/15115/
> 
> Once this patch got accepted, I intend to port it to Nova in the same
> fashion.
> 
> Now, Huang Zhiteng raises an issue that might also interest Nova team,
> so I'm bringing this to this list.
> 
> My patch plugs the audit in a periodic task under the cinder-volume
> daemon, since this is the one making more sense for cinder. For Nova,
> that would probably be nova-compute.
> The concern is that sending exists notifications might take too long and
> blocks the daemon for too much time.
> 
> From my point of view, since each host is only sending notifications
> about volumes (in Nova that would be instances) it handles, this is not
> going to be a lot of them, and that shouldn't take the daemon too long
> nor block it for a while. Compared to the burden of shipping another
> daemon.
> 
> Also, while I'm at it, suggestions about a default auditing rate might
> be welcome, since the default periodic_interval (60s) might be a little
> too low. Maybe using ticks_between_runs would be a good idea?
> 
> -- 
> Julien Danjou
> # Free Software hacker & freelance
> # http://julien.danjou.info
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev