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 > > Collects the contents of PATH in all other devices that are part of > the multinode job and store them at DEST locally. For example, the > call `lava-collect /var/lib/foobar /var/tmp` would result in > > /var/tmp > node01/ > var/lib/foobar > (stuff) > node02/ > var/lib/foobar > (stuff) > (...) How does the receiving node authenticate with each other node to get read access? 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 necessarily have access to anything on node02 without node02 being explicitly configured in advance to either serve files anonymously or allow login. I'm not sure this is appropriate as a helper across all LAVA deployments and if restricted to the same deployments as lava-network, it would require particular services to be installed and running on all nodes which lava-network does not enforce. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
signature.asc
Description: PGP signature
_______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
