Aurélien Degrémont

Thanks for this report! First of all, ValueError is not catch and should be. We will fix this. Regarding your proposal, this does not make sense for traditional upcall-based group...

Thanks for that! Really appreciate it. Please do not rename it `clusterssh` as there is already an other project with this name. Moreover do not think of this project as...

Actually, there is already an option for that: `--remote=yes|no` My question is: what should be the default value for this option with `clush`? Imagine the following scenario: - Admin1 creates...

After looking more closely to the code, `--remote` is also available for regular usage (with `--worker=ssh`). When enabling topology, as user, I expect that commands will be automatically routed to...

Do not rush on a patch for that. I need to think about it and all of this is not clear to me yet. Need to look at the code...

Getting back on this ticket, your summary looks good. I was wondering about a different approach. Should we modify the `distant_worker` with `-R|--worker` option? There is no way to control...

First of all, letters are not supported inside brackets. Names are first parsed, then compared to see how they matched. Even if your example could look easy, real algorithm to...

This can only be done using python code for now. I can propose to you a ugly hack, using exec worker: `clush -R exec -w node[1-10] 'ssh %host ./run.sh %rank'`

I mean clustershell API (in Python :)) ``` python from ClusterShell.Task import NodeSet, task_self for i, node in enumerate(NodeSet("foo[1-30]")): task_self().shell("./run.sh %s" % i, nodes=node) task_self().run() ``` (untested :))

I think your ticket is a duplicate of #293 .