Open Stack

Some similar discussion on periodic task happens on ceilometer side also , see http://lists.openstack.org/pipermail/openstack-dev/2012-November/002937.html 

--jyh

> -----Original Message-----
> From: Michael Still [mailto:michael.still at canonical.com]
> Sent: Tuesday, November 20, 2012 10:57 AM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] A new nova service? nova-periodic?
> 
> I don't much mind what we call it by the way.
> 
> Josh raises a valid point in bug/1080921 -- nova-compute periodic tasks
> block incoming API requests from being handled, which is probably
> something that you'd never want to see happen in a production deployment.
> 
> There's been some back and forth about this in terms of libvirt image
> cache management, but it seems that many of the periodic tasks fall into
> a category of "I want this to run, but I don't want to block servicing
> API requests for it".
> 
> What do people think about adding another nova service which runs beside
> nova-compute and runs periodic tasks which don't need any sort of shared
> global state with nova-compute? We could do it with a flag so that the
> default remains to use nova-compute for these periodic tasks, but if you
> "opt in" they're done with a nova-periodic instead.
> 
> Thoughts?
> 
> Michael
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev