> how tricorder handles calls to multiple nodes

Sequentially, one after the other, then it aggregates the `Result<(exit_code, output), Error>` type into a JSON.

Once I take a look at async programming in Rust, it should be trivial to add the concurrent option: just start them all, wait for them, and aggregate as before.

Still not sure if it should be the default or not, should it be a `--sequential` or a `--parallel` flag? IIRC, Ansible does things sequentially too.