Bug 632675 - Re-architect beaker results reporting/storage
Summary: Re-architect beaker results reporting/storage
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: lab controller
Version: 0.5
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bill Peck
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 632609
TreeView+ depends on / blocked
 
Reported: 2010-09-10 17:53 UTC by Bill Peck
Modified: 2011-09-28 15:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-28 02:02:13 UTC
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.