Comment 3 for bug 883474

My own plans for this sort of thing have been to have the dispatcher communicate (using the --oob-fd thing I added for reporting the bundle url) which action it was executing, and then divide up the log by action. We could then present the output in the scheduler as an accordion type thing so you could instant zoom in on say the logs of the deploy action. It would also be nice to fold away the reboot logs by default as they really get in the way a lot of the time.

Any move from the current approach where we just dump unstructured data into a file would probably be quite difficult though -- I guess we could continue to do that, but also record a series of offsets into that file to know which bits to display? That sounds possible, but it would also be nice to display log messages, commands we execute and output from said commands differently, and that seems to push towards a more structured format -- maybe something a sequence of json things?

{'type': 'logmsg', 'content': '<INFO> executing linaro-media-create'}
{'type': 'command', 'content': 'root@linaro# [rc=0] linaro-media-create ...'}
{'type': 'output', 'content': 'Unpacking rootfs...'}

Maybe this is overkill though?

Apologies for the brain dump.