I think you sort of answered your own question - serial: is related to
a given play,
so if that play is targeted against a group then tasks against thet
group will complete
on each server before the next one starts.A good example is bouncing
servers while
leaving enough active to keep your load balancer happy
I've always thought of forks as more to do with the ansible control
host; if things can
run in parallel they will, and you can safely ramp that up as high as
you like as long
as the control host has enough resources. This pays off well for e.g.
package installs.
I might be missing something about your use case; why wouldn't you always want
a serial: tagged play to run - well, serially?
> --
> You received this message because you are subscribed to the Google Groups "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
ansible-proje...@googlegroups.com.
> To post to this group, send email to
ansible...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/576AE046.7020708%40ojkastl.de.
> For more options, visit
https://groups.google.com/d/optout.