On Wed, 27 Nov 2013 13:01:36 -0300
Antonio Terceiro antonio.terce...@linaro.org wrote:
For 3. I think it would make sense to have an API call that you could
use from your data analysis node that would retrieve a given directory
from the other nodes. Something like
lava-collect PATH DEST
On Wed, 27 Nov 2013 13:29:16 -0300
Antonio Terceiro antonio.terce...@linaro.org wrote:
On Wed, Nov 27, 2013 at 04:13:14PM +, Neil Williams wrote:
Data cannot go over the existing API connection, it has to be
configured separately over something like TCP/IP and root on node01
does not
Neil Williams codeh...@debian.org writes:
On Wed, 27 Nov 2013 13:56:42 +1300
Michael Hudson-Doyle michael.hud...@linaro.org wrote:
I've been looking at moving my ghetto multinode stuff over to proper
LAVA multinode on and off for a while now, and have something that I'm
still not sure how
Antonio Terceiro antonio.terce...@linaro.org writes:
On Wed, Nov 27, 2013 at 01:56:42PM +1300, Michael Hudson-Doyle wrote:
Hi,
I've been looking at moving my ghetto multinode stuff over to proper
LAVA multinode on and off for a while now, and have something that I'm
still not sure how best
Neil Williams codeh...@debian.org writes:
(sure we could find better names than lava-collect and lava-serve)
lava-nc-listen - offers files on a known port, opens the port
lava-nc-connect - makes connections to each node using the port.
lava-sync processing-done
lava-sync
