News for hackers. Stuff that matters.
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.

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.
Re:A Python library for writing distributed self-replicating... by zeckalpha on Friday November 22, 2019 @11:06PM (#21612404)
What's preventing that?
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

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!