4 ms·
Too heavy, too complex and too slow. Although ansible can be used in local machine, but it is design for multiple remote machine. For example, if you want copy
by nanozuki 4y ago
Too heavy, too complex and too slow.
Although ansible can be used in local machine, but it is design for multiple remote machine. For example, if you want copy a config file to target, you must use some tools like `scp` or do some hacking. And it's much slow than shell script, and the print in stdio is ugly. (because it's design for running in 100 machines in one time.)
Ansible also had a steep learning curve, and redhat did not prepare a good beginner's manual for it. Searching the web there is only the experience of people who have used it for years, each with their own way of writing. There are no best practices for getting started easily.
- lmz 4y agoAnsible has a steep learning curve? The easiest thing to do is just a list of steps (playbook) and I'm sure that is in the getting started docs. Modularizing complicates things obviously but for simple uses I don't see how it can be simplified much further.
- allarm 4y agoYes, it was harder to master than terraform and even k8s. Their documentation was the reason, in most cases.
- yunohn 4y ago> if you want copy a config file to target, you must use some tools like `scp` or do some hacking Maybe I misunderstood, but I use copy (1) for this in Ansible. This is standard, and you shouldn’t need scp? (1) https://docs.ansible.com/ansible/latest/collections/ansible/builtin/copy_module.html https://docs.ansible.com/ansible/latest/collections/ansible/...