Server-side probe logging

[dclark]

It would be *really* useful if the output of Probes could be kept in server-side state somewhere; either spewed to the bcfg2-server verbose logs (or perhaps add another level of verbosity that would just include the entire client log output), or included in the new dynamic reports.

I have a preference towards bcfg2-server log spewing as a first step, as this is functionality that would be really useful when first setting up bcfg2 at a site, and there may be a lag between getting bcfg2-server up and getting the new reports working.

I have a large number of different platforms to work with - like at least 20 (I'm not kidding) - and this would save me from having a whole lot of ssh sessions open when debugging Bcfg2 Probes.

This would also have increased utility when the proposed daemon mode is written - I have the equivalent now via ostiary (a simple daemon that kicks off arbitrary preset commands based on a simple secure hash), so am probably running into this need before other people.

[dclark]

Another more generalized idea would just be to have a delayed version of OpenAFS's ​bos getlog command; something like:

# bcfg2-admin getlog machinename:/path/to/text/file
(wait till next run)
(file gets placed somewhere like 
 /var/lib/bcfg2/var/getlog/MACHINENAME/path/to/text/file/DATETIME)

[dclark]

First step bcfg2-server logging added in r3398

[dclark]

Reassigning to reports / joey's consideration.

[desai]

We are going to start stashing copies of probe results on the server so that we have a baseline to use in template debugging. This should provide the data needed to close out this ticket as well.

[desai]

Implemented in [448dc7da6b40de27d73b20a6db69be716e7527c4] (SVN r3647).

[https://www.google.com/accounts/o8/id?id=AItOawnEusV609cT6ichWkkp_Whof8y86hcPhFk]

​What is spyware