4 ms·

The use-case is mainly to get rid of the inherent bottleneck that Ansible has, where you have to execute everything from a single manager node. It also contains

The use-case is mainly to get rid of the inherent bottleneck that Ansible has, where you have to execute everything from a single manager node. It also contains tons of optimizations at the networking level, etc. It makes sense if you've got 1000s of nodes you're managing with Ansible, and you need to increase efficiency. If you've ever tried running an Ansible playbook against even 100 hosts, you'll know it can be painfully slow even with SSH pipelining. Mitogen makes that much much faster. AFAIK Operon[1] is just a better version of that (with the possibility of personalized support contracts, etc). Disclaimer/Source: I'm friends with the author of Mitogen/Operon. [1] https://networkgenomics.com/operon/ https://networkgenomics.com/operon/

thephyber 7y ago
I also found this, which agrees with you: https://dev.to/sshnaidm/speed-up-ansible-with-mitogen-2c3j https://dev.to/sshnaidm/speed-up-ansible-with-mitogen-2c3j
zeckalpha 7y ago
That's not an inherent bottleneck in Ansible. https://docs.ansible.com/ansible/latest/cli/ansible-pull.html https://docs.ansible.com/ansible/latest/cli/ansible-pull.htm... There are other benefits of using this automation, namely that it removes manual application of changes.
- perlgeek 7y ago
  The problem with ansible-pull is that you can no longer use it coordinate changes across machines, which is very useful for deployments for example.
  - zeckalpha 7y ago
    What's preventing that?
- dmw_ng 7y ago
  I mean sure, just copying Ansible to the target machine and running it locally 'fixes' things, but at what point should it still be considered Ansible? You lose so much with -local, at least: - centralized vault, target nodes need access to secrets - "serial:" no longer available, you can't do rolling upgrades any more - "hostvars" no longer available, you can't query facts from other machines - no centralized trigger mechanism, status or failure reporting etc. Put another way, you could claim ansible-local fixes things for the same reason you could claim bash is network-aware agentless automation because you can copy shell scripts between machines
  - aeontech 7y ago
    Time to add “skilled in network-aware agentless automation” to my resume!

thephyber 7y ago

I also found this, which agrees with you: https://dev.to/sshnaidm/speed-up-ansible-with-mitogen-2c3j https://dev.to/sshnaidm/speed-up-ansible-with-mitogen-2c3j

zeckalpha 7y ago

That's not an inherent bottleneck in Ansible. https://docs.ansible.com/ansible/latest/cli/ansible-pull.html https://docs.ansible.com/ansible/latest/cli/ansible-pull.htm... There are other benefits of using this automation, namely that it removes manual application of changes.

perlgeek 7y ago
The problem with ansible-pull is that you can no longer use it coordinate changes across machines, which is very useful for deployments for example.
- zeckalpha 7y ago
  What's preventing that?
dmw_ng 7y ago
I mean sure, just copying Ansible to the target machine and running it locally 'fixes' things, but at what point should it still be considered Ansible? You lose so much with -local, at least: - centralized vault, target nodes need access to secrets - "serial:" no longer available, you can't do rolling upgrades any more - "hostvars" no longer available, you can't query facts from other machines - no centralized trigger mechanism, status or failure reporting etc. Put another way, you could claim ansible-local fixes things for the same reason you could claim bash is network-aware agentless automation because you can copy shell scripts between machines
- aeontech 7y ago
  Time to add “skilled in network-aware agentless automation” to my resume!