concurrent tasks?

Archives AWX Project
1

When I run a playbook in tower, it seems like its always runs concurrently 5 tasks at a time. Unfortunately, I have 6 servers in my inventory, so when I get to a task like this:

  • name: restart server
    win_reboot:
    pre_reboot_delay: 300
    post_reboot_delay: 60
    reboot_timeout: 3600

It waits 5 minutes (pre_reboot_delay) for 5 of the servers and reboots them, then waits for them to come online - and only after that does it start the 5 minute wait for the 6th server… So the whole task takes a minimum of 12 minutes ((pre_reboot_delay + post_reboot_delay)*2 server groups)

I’m having trouble figuring out which setting this is… anyone have any idea?

2

Correction "it seems like its always runs concurrently 5 tasks at a time. " should be "it seems like its always runs concurrently 5 nodes at a time. "

3

It's ansible default behavior. You change it for ansible cli command or for awx job template.

https://docs.ansible.com/ansible-tower/latest/html/userguide/job_templates.html

Forks: The number of parallel or simultaneous processes to use while executing the playbook. A value of zero uses the Ansible default setting, which is 5 parallel processes unless overridden in /etc/ansible/ansible.cfg.

4

For long running tasks (in my use-cases this is usually the installation/update of packages) I like to use async to get them running on all targets while not needing hundreds of forks. I am not sure if this works with win_reboot though :slight_smile:

Greetings

Klaas