If it's only one task that takes very long, and you don't have any follow up tasks that rely on the outcome of the previous task, you might want to set async: true
for that task.
Ansible
# TODO
No, it's a moderately complex role. Could I include the role with async: true
? There is obviously some dependencies inside the role, but not between the different role inclusions.
I think you can use async
on task level only, but the documentation would be wider than me on that detail.
I just had another idea: you could use the Mitogen execution strategy. It doesn't make your tasks run in parallel, but it takes away a lot of the overhead involved in running Ansible, so you might get some performance gains there. It's not running your tasks in parallel though...
For real parallel execution, you would probably need multiple hosts. I don't think what you're trying to do is even a part of Ansible on the conceptual level.
Could one maybe use multiple hosts in the ansible inventory that point to the same host?
Maybe k8s ist better suited for this.
Yes, you could setup multiple DNS aliases in your nameserver/router or in your /etc/hosts
file that point to the same IP; DNS might round-robin through the IPs, but I've never tried this.
EDIT: You're right, the DNS aliases go in the Ansible inventory, no need for DNS round-robin. Short brainfart, sry. EDIT END.
I have near-zero experience with k8s (apart from a little bit of Minikube, which I hated), so I can't say anything about that option, but my impression is that it's massive overkill for almost all use cases, aka "you're not Google".