3 ms·
In general, I like Ansible's concepts of idempotency, etc., and find them to be well suited for server configuration in general, but it does come at a price, bo
by dmitrig01 12y ago
In general, I like Ansible's concepts of idempotency, etc., and find them to be well suited for server configuration in general, but it does come at a price, both in terms of development time and speed (I actually find Ansible to be a lot slower than Fabric).
I've started thinking of server configurations in Ansible terms (i.e. "I want X module installed, Y directory present, etc"), but sometimes nothing beats a simple bash command to git pull && sudo service restart.
- Gigablah 12y agoAnsible was pretty slow for me too. Then I discovered pipelining=True :)
- nivertech 12y agoWhat pipelining=True does? EDIT: nevermind, found it: http://docs.ansible.com/intro_configuration.html#pipelining http://docs.ansible.com/intro_configuration.html#pipelining
- mpdehaan2 12y agoHere's a good blog post on the subject: http://www.ansible.com/blog/ansible-performance-tuning http://www.ansible.com/blog/ansible-performance-tuning If you want to use paramiko (like Fabric does), you can -c paramiko too. This mode came first, but -c ssh offers more features and can be just as quick.
- krakensden 12y ago> I actually find Ansible to be a lot slower than Fabric Have you tried it since they switched to using ssh by default (instead of paramiko)? Because in my experience Ansible can ship multiple modules faster than Paramiko can connect to a host. And it is vastly easier to build reliable tasks out of modules than bash scripts.