Periodic tasks integration in Service class
Bug #1050366 reported by
Mark McLoughlin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oslo-incubator |
Won't Fix
|
Medium
|
Unassigned | ||
| oslo.service |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
The Service class's periodic tasks integration was removed here: https:/
Because we didn't want the base Service class knowing anything about the Manager class which is for RPC only
Basically, we want some way for the base class to know about all the objects which may implement the run_periodic_
In the case of rpc.Service, that's just the manager object. In the case of wsgi.Service, maybe that would be all objects in the application pipeline?
Revision history for this message
| Angus Salkeld (asalkeld) wrote | #1 |
| affects: | openstack-common → oslo |
| Changed in oslo-incubator: | |
| status: | Confirmed → Won't Fix |
| Changed in oslo.service: | |
| status: | New → Won't Fix |
To post a comment you must log in.
I personally find periodic a bit odd as it is not very controllable - you
don't know how often it is going to be called. I prefer the idea of a timer
as you know exactly how it is called and is not at the whim of the admin.
In nova we can define a Manager class that inherits from PeriodicTasks
the question is do other projects want a periodic api or timer api?
Any reason we can't just use the timer_add() method?