-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
2.4
-
None
-
False
-
-
False
Feature Request Details:
Running multiple jobs in parallel within a single template simplifies troubleshooting, particularly when dealing with job failures. This will help us bypass the delays associated with sequential execution, ensuring that tasks are completed more quickly, and issues are easier to identify and address.
For eg, when executing a template for 100 hosts, it's much easier to identify and troubleshoot issues if you can run the tasks in different parallel batches(jobs), rather than waiting for a single job to complete for all 100 hosts.
And job should be configurabale according to inventories and groups.
Reason for not using workflow:
Not using workflows because they would require creating multiple job templates, which could lead to confusion and an excessive number of templates to manage. So, we'd prefer a solution that will allow us to have a single template with multiple jobs.
Reason for not using slices: Slice has its own logic to divide hosts and create parallel jobs.