Bug 632675

Summary: Re-architect beaker results reporting/storage
Product: [Retired] Beaker Reporter: Bill Peck <bpeck>
Component: lab controllerAssignee: Bill Peck <bpeck>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: 0.5CC: bpeck, dcallagh, kbaker, mcsontos, rmancy
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-28 02:02:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 632609    

Description Bill Peck 2010-09-10 17:53:01 UTC 
Description of problem:
Suggestion is to have a separate machine for logs.

Instead of pushing all logs to the Scheduler we would store them in the labs and point back to them from the Scheduler.
Comment 1 Bill Peck 2010-09-21 16:55:43 UTC 
Update lab controller/proxy to cache active recipe logs on the lab controller itself.  

cron job run daily would push all logs for finished recipes to results server.  This can be either the scheduler or another server for hosting results. (determined via config option)

pseudo code

for recipe in recipes_finished_but_not_migrated:
   rsync recipe to result server
   update DB location for logs
   delete recipe logs from cache