Ansible itself has no restriction on running concurrently, there are
several ways to solve this issue, most depend on your context:
- use ansible-pull with a cron/scheduler on each machine using
setlock/lockf/etc to guarantee a single execution on itself
- If using a single 'management
Thanks for the suggestion, and taking the time to understand the problem.
File-existence/absence locks have a giant problem: The state is only very
loosely tied to the creating or waiting process. i.e. the creator can die,
but leave the file there. That blocks everyone else indefinitely
Not seen anything like this, but wondering if you can make do by using
wait_for on a file.
http://docs.ansible.com/ansible/wait_for_module.html
On Tuesday, May 30, 2017 at 8:23:20 PM UTC+1, cev...@redhat.com wrote:
>
> In other words:
>
> Job-scheduling system can use a playbook like this:
