3 ms·
For me the hardest part about Ansible was getting the ssh setup correct to connect to a remote machine. Having a quick browse of this tutorial I can't see much
by collyw 9y ago
For me the hardest part about Ansible was getting the ssh setup correct to connect to a remote machine. Having a quick browse of this tutorial I can't see much about that (maybe I missed it). That would be useful if you plan to update the tutorial.
- emmelaich 9y agoI put everything into git; the ssh-config file, the keys, the hosts file. I then wrote a wrapper (also in git) that invoked ansible with all the correct/preferred settings. Works a treat.
- lolikoisuru 9y agoThe ssh configuration is one of the reasons I still haven't been able to move to Ansible properly. I managed to get it working somewhat without any controlmasters but I would much prefer having those, they significantly speed up making the connections when jumping through 2 hosts. Even without controlmasters when using higher parallellism than the default 5 it the ssh connections start to fail for no apparent reason. E: And another reason I would love to not use Ansible is the god awful YAML. It's a horrible choice for a tool like this.
- tokenizerrr 9y agoAs far as I know all you have to do is configure your ~/.ssh/config properly, and then use the hostnames set there. Same as regular old OpenSSH. Just don't opt into the Paramiko control scheme, which isn't used by default except on RHEL6 anyway. You can also set ssh_args in the config file to enable ControlMaster, etc. http://docs.ansible.com/ansible/latest/intro_configuration.html#openssh-specific-settings http://docs.ansible.com/ansible/latest/intro_configuration.h...
- beefhash 9y agoTruly, this is the modern-day equivalent of setting up UUCP.