ansible my_servers -m shell -a 'fortune && reboot' -b I know it is easy to be a hater, but sincerely do not see a reason to use something like that over Ansible or just pure sh, ssh and scp. All you have to do is to set up keys and the inventory. Takes 10 minutes, even if you are doing it for the first time. And you can expand it if you need it.
Ansible requires python to be installed on all of the target computers.
Show HN: Sshsync – CLI tool to run shell commands across multiple remote servers
41–50 of 77 posts
Re: Show HN: Sshsync – CLI tool to run shell commands across multiple remote servers
#42Personally, I'm a tmux synchronized-panes kind of guy, so that I can see the result of each output immediately.
Re: Show HN: Sshsync – CLI tool to run shell commands across multiple remote servers
#43To me GNU parallel is the top of the line here (as it is for most things parallel). For the most common cases I have it aliased to just `p`: https://github.com/Julian/dotfiles/blob/main/.config/zsh/com... Or https://github.com/Julian/dotfiles/blob/4d36e6b17e9804a887ba...
what is the use case? why wouldn't you use something else (like ansible or puppet or something)? I do not understand why someone would do things like this.
Re: Show HN: Sshsync – CLI tool to run shell commands across multiple remote servers
#44I didn't really expect them to write code on the spot (hate that in interviews), but just to describe a possible solution; there were no wrong answers. Seeing how people came up with a quick hack for 10 and then being able to evolve their thinking for thousands was the point of the question and it could be enlightening to see.
I had a lot of people come up with things that I never even thought of, such as SSH'ing in to all 10 machines and then using a terminal feature to type into all of the windows at once.
Re: Show HN: Sshsync – CLI tool to run shell commands across multiple remote servers
#45Re: Show HN: Sshsync – CLI tool to run shell commands across multiple remote servers
#46Earlier quoted context omitted.
what is the use case? why wouldn't you use something else (like ansible or puppet or something)? I do not understand why someone would do things like this.
Why would anyone use Ansible or Puppet for running shell commands on remote servers? Such an overkill.
and I would be afraid to run SSH commands on multiple machines at once in case one of them errored out and needed manual intervention. ansible or puppet would let me know about that stuff.
Re: Show HN: Sshsync – CLI tool to run shell commands across multiple remote servers
#47Earlier quoted context omitted.
Why would anyone use Ansible or Puppet for running shell commands on remote servers? Such an overkill.
well usually it's already in place, right? maybe at home it wouldn't be, but at work, that stuff would already be in place on the stock OS install. and I would be afraid to run SSH commands on multiple machines at once in case one of them errored out and needed manual intervention. ansible or puppet would let me know about that stuff.
Re: Show HN: Sshsync – CLI tool to run shell commands across multiple remote servers
#48In a past life, this is an interview question that I would ask people: "We have thousands of servers, and you need to run the same command on 10 of them, what's one way you would do it?" and follow up with "What if you wanted to run the command on hundreds or thousands - what problems would you expect with this approach, and what might you do differently?" I didn't really expect them to write code on the spot (hate t…
Re: Show HN: Sshsync – CLI tool to run shell commands across multiple remote servers
#49http://guichaz.free.fr/polysh/