So let’s say you have the following situation:
- You have some sizable number of hosts, with some particular software that contains its own set of playbooks. - There may be differences in the software versions, and thus playbooks can differ between sets of these remote hosts. - You also have inventory and playbooks outside of these hosts, in your local environment. - You want to run both the local and remote playbooks using the same (local) inventory. In the situation where you don’t care about local inventory or context, I guess kicking off a remote execution of Ansible using the shell module or SSH would be an option. But if you _did_ care about the current operating context, it would be interesting if Ansible were able to start a remote “slave” runner that would then run the remote playbooks/roles using the inventory and context delivered from your current local Ansible running instance (the parent/master). The remote runner would run the remote plays with the host/inventory_hostname set to the remote host's, but at least you’d be able to share context such as facts, variables and inventory and be able to run plays/roles that exist on the remote side. (Just an idea.) On Wednesday, April 2, 2014 4:22:44 PM UTC-4, Michael DeHaan wrote: > > Calling Ansible with Ansible? > > There is no suggested course of action, but I suspect you would do exactly > that. > > I'd really want to understand the *why* though. > > > > > > On Wed, Apr 2, 2014 at 1:32 PM, <[email protected] <javascript:>> wrote: > >> Purely out of curiosity, what is the suggested course of action to run >> playbooks present on a remote host within a current run of a local Ansible >> play? >> >> The worst case being to use the shell module to actually exec Ansible >> remotely with the remote playbook, are there more elegant approaches? >> >> -- >> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected]<javascript:> >> . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/5bb90b4c-d9a8-4b9a-9667-d19664504dbe%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/5bb90b4c-d9a8-4b9a-9667-d19664504dbe%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/7a17c3e8-b323-4ab3-9694-b3b06d1ba837%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
