In labcontroller.conf we specify the following; # Set CACHE = True only if you define ARCHIVE_* variables correctly! I was wondering if there's any reason why we have to tie storing logs on the lab controller (as opposoed to the server) to the running of beaker transfer? In the most general sense, is storing the files on the lab controller not a legitimate scenario ?
(In reply to comment #0) > In the most general sense, is storing the files on the lab controller not a > legitimate scenario ? This makes sense to me. If we removed support for sending logs to the Beaker server (meaning, you either leave them permanently on the lab controller, or enable beaker-transfer to ship them elsewhere) that would eliminate some code paths and help simplify the log uploading code.
(In reply to comment #1) > (In reply to comment #0) > > In the most general sense, is storing the files on the lab controller not a > > legitimate scenario ? > > This makes sense to me. If we removed support for sending logs to the Beaker > server (meaning, you either leave them permanently on the lab controller, or > enable beaker-transfer to ship them elsewhere) that would eliminate some > code paths and help simplify the log uploading code. Agree, and for most users who run the scheduler and lab controller on the same machine it still wouldn't change anything either, just makes the code simpler as you mention.
Bulk reassignment of issues as Bill has moved to another team.
I wrote a patch for this while working on the harness API: http://gerrit.beaker-project.org/1701
Beaker 0.12 has been released.