You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ansible provisioner in Vagrant is designed to run once per each host by default.
We did worked this around by having ansible.limit='all' in 9607d41
This introduced another issue: provisioner will run that number of times, how much vms are defined in :vms: [] array in omv.yml.
Quick and dirty patch us attached (just to demonstrate the idea), but it introduces another issue: with this it's impossible to define multiple playbooks per host in the omv.yml (one global in :playbook: [] array, and one "per-vm" playbook in :vms: array.
Now I don't really see the use case of having multiple playbooks per host (as you do in examples/ansible.yml - if you agree I will submit a merge request with this patch.
If you disagree - please share your thoughts with me so I can think of another solution. ansible_provisioner_number.txt
Thanks.
vk
The text was updated successfully, but these errors were encountered:
hey @br0ziliy, to be honest, i don't have any strong opinions about this because i'm not really using the ansible functionality at the moment. I think if you had a more concrete example of what problem is difficult to solve with the current code, it might help me understand better.
Having said all that, since I'm focusing my attention on https://github.com/purpleidea/mgmt most of the time, I'm happy for you to have the final call for ansible design/patches.
Hi James,
Ansible provisioner in Vagrant is designed to run once per each host by default.
We did worked this around by having
ansible.limit='all'
in 9607d41This introduced another issue: provisioner will run that number of times, how much vms are defined in
:vms: []
array in omv.yml.Quick and dirty patch us attached (just to demonstrate the idea), but it introduces another issue: with this it's impossible to define multiple playbooks per host in the omv.yml (one global in
:playbook: []
array, and one "per-vm" playbook in:vms:
array.Now I don't really see the use case of having multiple playbooks per host (as you do in
examples/ansible.yml
- if you agree I will submit a merge request with this patch.If you disagree - please share your thoughts with me so I can think of another solution.
ansible_provisioner_number.txt
Thanks.
vk
The text was updated successfully, but these errors were encountered: