thiell

Hmm, ok I understand better, and I think you're right. I just tested `--worker exec` and it doesn't work by default, I need to add `--remote=no` (my topology.conf is using...

btw there is not `-W` short option for `--worker`, it's `-R`. Let me know if you want to add it as an alias.

Hmm, Not sure I understand better. I will have to do some tests. I pretty sure `--remote=yes/no` was designed for distant workers only, and `remote=no` switches to a local worker...

One more word, for me, Admin2 should use: `clush ... --remote=no ipmitool -I lan -H %h power status ` (installing a topology.conf will launch this command on gateways) instead of:...

What about doing this: - `-R ` does specify the worker, it can be either exec, ssh, tree or **auto** (default) - `--remote yes|no` only works with auto or tree...

But if the following is found in defaults.conf: ``` [task.default] distant_workername: rsh ``` that will switch to rsh worker in tree mode.

updated comments

Planned for 1.7.2, no problem. It's already usable as is. :)

I don't want to do major changes in 1.7.2, just bug fixes or doc improvements. @degremont: is it ok to change the milestone to 1.8? My change proposal above is...

Thanks @asteven for the suggestion. I never used click before. I tried to migrate clustershell's cli to argparse with no functional changes but it's tough.