Comment 2 for bug 1112473

After studying benchmark implementation in CBuild, I got an idea that it makes sense to use rsyncd not only 1) to distribute build prerequisites to boards; 2) distribute settings to boards; but also to: 3) publish build logs/benchmark results from boards; 4) publish result binaries from boards. Such scheme essentially follows native CBuild way, and bypasses LAVA server for transfer of results completely. The latter seems "not good", but actually it seems to be the most practical way for now (while LAVA has issues with API coverage, and with current aim being just use LAVA as builds backend).

Some difference with native CBuild publishing is that it uses rsync+ssh for transfer, which is considered security issue for LAVA boards, so the idea is to use write-only rsync modules.