5 ms·
Ansible has a very low barrier to entry in terms of dependencies that need to be installed into the machines you want to manage: they need to have python 2.6+ o
by shoo 5y ago
Ansible has a very low barrier to entry in terms of dependencies that need to be installed into the machines you want to manage: they need to have python 2.6+ or python 3.5+, and you need to be able to connect to the machines over ssh.
One way to get started could be to initially ignore ansible playbooks, just install ansible onto your control machine. Write an inventory file with one or more hostnames of machines you want to manage. See if you can get ansible to connect with ssh and "ping" all the machines. Once you're comfortable with executing one-off commands through ansible, the jump to ansible-playbook will be smaller.
- MaknMoreGtnLess 5y ago> Ansible has a very low barrier to entry in terms of dependencies that need to be installed into the machines you want to manage: they need to have python 2.6+ or python 3.5+, and you need to be able to connect to the machines over ssh. I understand what you're saying but do understand that to other people these can be concepts that they arn't familiar with or might actively struggle with That said - were there any obstacles you faced when you started with Ansible? What could have been better (tooling/docs/training/etc) to get you upto speed better/faster?
- skydhash 5y agoShameless plug: https://hescaide.me/blog/2022/01/29/a-day-with-ansible/ https://hescaide.me/blog/2022/01/29/a-day-with-ansible/ This is after one day of interacting with Ansible. I did have previous experience with Linux and setting up Circle.ci projects and Dockerfile. There are not many concepts to grok. I just cloned a playbook on GitHub and tried to rewrite it to fit my needs, reading documentation over the part I did not understand well. No book or video tutorials were needed.
- MaknMoreGtnLess 5y agoMuch appreciated!