periodic tasks could use a refactoring
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Michael Still |
Bug Description
Right now, you declare periodic tasks with the @manager.
The issue I have is that changing FLAGS.periodic_
Rough ideas of what I'd like to do for Folsom:
change @manager.
Modify the task runner to be a bit more smart. Since it has a list of periodic tasks to run (and it can ignore ones that are enabled=False).. it can figure out the amount of time it needs to sleep to run the next task. Essentially the task runner can sit in a greenthread sleeping until the next periodic task should run based on its "interval" setting.
Something like that :) Other ideas welcomed!
Changed in nova: | |
importance: | Undecided → Low |
status: | New → Triaged |
Changed in nova: | |
milestone: | none → grizzly-2 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | grizzly-2 → 2013.1 |
Another example: If you want a periodic task to run at 5 seconds, but poll_interval is 60s.. you can't do that right now without modifying poll_interval down to 5s. Then you would need to go up the 'ticks' for every other task by 12x.