this should be quite easy to implement, with the only concern being what to do with the aggregated shell script responses. currently, jclouds' ComputeService.runScriptOnNodesMatching() function returns a Map<? extends NodeMetadata, ExecResponse> where the exec response may have an unsuccessful error code inside.

I have a compute example called exec for this. you may want to add a flag as to whether the command is long-running or not. For example, executing "uptime" doesn't need to be run init style, so you'd want to set wrapInInitScript(false).

https://github.com/jclouds/jclouds-examples/blob/master/compute-basics/src/main/java/org/jclouds/examples/compute/basics/MainApp.java

A bit ugly but working patch. I will refactor the code soon. Let me know what you think.

The code is only tested on AWS but it should work anywhere thanks to jclouds.

I believe that for now it's safe to assume that all scripts executed with this command are short-running.

Looks good. Needs a unit test like the other commands. Should we print out stdout and stderr, regardless of exit code?

Nit: Rather than saying "script.sh" in the usage string say "<script>" so it's less literal.

I've updated the patch and added some tests. I'm moving to WHIRR-246.

Good to go in?

Sorry, missed the update. +1

I've just committed this.