A Python library for writing distributed self-replicating programs

Re:A Python library for writing distributed self-replicating... by anaphor on Tuesday November 19, 2019 @08:07PM (#21580183)

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/

[ Parent | on HN ]

Re:A Python library for writing distributed self-replicating... by zeckalpha on Wednesday November 20, 2019 @02:05AM (#21581707)

That's not an inherent bottleneck in Ansible. 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.

[ Parent | on HN ]

Re:A Python library for writing distributed self-replicating... by perlgeek on Wednesday November 20, 2019 @03:23AM (#21582071)

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.

[ Parent | on HN ]

Re:A Python library for writing distributed self-replicating... by zeckalpha on Friday November 22, 2019 @11:06PM (#21612404)

What's preventing that?

[ Parent | on HN ]

Re:A Python library for writing distributed self-replicating... by dmw_ng on Wednesday November 20, 2019 @10:39AM (#21584813)

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

[ Parent | on HN ]

Re:A Python library for writing distributed self-replicating... by aeontech on Thursday November 21, 2019 @09:30PM (#21601925)

Time to add “skilled in network-aware agentless automation” to my resume!

[ Parent | on HN ]

Re:A Python library for writing distributed self-replicating... by thephyber on Tuesday November 19, 2019 @08:23PM (#21580272)

I also found this, which agrees with you:

https://dev.to/sshnaidm/speed-up-ansible-with-mitogen-2c3j

[ Parent | on HN ]