Closed Bug 913601 Opened 11 years ago Closed 7 years ago

slaveapi should store history somewhere

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned, Mentored)

Details

Right now, results of actions are volatile - they disappear when the daemon is restarted. We should store them somewhere. I did some initial investigation into this and I'm leaning towards a simple SQL backend. I looked at using redis too, but it doesn't seem like a good choice for data that will live for a long time.
Whiteboard: [mentor=bhearsum]
No longer blocks: 914805
Where "somewhere" is not on the hosts themselves, plz
Mentor: bhearsum
Whiteboard: [mentor=bhearsum]
Component: Tools → General
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.