Setting up a purge cron job complicates installation
Bug #1239377 reported by
Clint Byrum
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Won't Fix
|
Low
|
Unassigned |
Bug Description
For simplicity sake, Heat should just setup a background purge process automatically. The engine could simply fork off a process that runs in the background and sleeps, waking up at a configured interval to clear out recently expired deleted items. This would make Heat much easier to install and reduce external dependencies.
To post a comment you must log in.
I realise you have a lot more experience in operations than I, but I respectfully disagree with this. IMO some things should be deferred to external tools because (a) only the operator can make the right decision, and (b) there are battle-hardened, standard system tools to do the job far better and more reliably than anything Heat could hope to replicate.
We now support multi-engine installations - would _every_ Heat engine be periodically purging the DB?