Open Stack

+1!  We'd have this for other projects, at least Cinder as well.

On Tue, Nov 20, 2012 at 11:25 AM, Joshua Harlow <harlowja at yahoo-inc.com> wrote:
> +1 for this, wonder what code would have to be re-factored to make this
> possible (some small library that nova-periodic would use?).
>
> The other nice benefit would also be that it moves more things that have
> to do eventlet 'oddness' (ie greenthread.sleep) out of nova-compute 'land'.
>
> On 11/19/12 6:57 PM, "Michael Still" <michael.still at canonical.com> wrote:
>
>>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



-- 
Regards
Huang Zhiteng