I'm totaly agree with you. On Thursday, June 6, 2013 2:23:17 PM UTC+1, Michael DeHaan wrote: > > Yeah I don't know, is there a vagrant list to coordinate that on instead? > > This is really not a part of Ansible. > > I understand many people like it, but I personally like to use virtual > machine snapshots instead for testing, and avoid the extra layers of > abstraction that (to me) make things require more hoops to jump through. > > You can then just revert those VMs back to normal if you want to do a new > clean test. > > Tim Gerla was doing some very nice things with "vmrun" exactly for this > purpose. > > > > > On Thu, Jun 6, 2013 at 9:11 AM, Peter Petrov <[email protected] > <javascript:>> wrote: > >> On Thursday, June 6, 2013 12:51:46 PM UTC+3, Gilles Cornu wrote: >> >>> >>> About the `ansible.use_vagrant_inventory` idea: I also aim at in DRYing >>> at maximum the collaboration between Vagrant and Ansible (at least for >>> playbook development tasks). In Vagrant-1.2 the ansible provisioner, >>> `ansible-playbook` is called for each VM to provision (I guess it is the >>> same with dsander-like vagrant plugin, but I haven't verified yet). In >>> multi-machine mode, that leads vagrant to run ansible-playbook several >>> times against the whole inventory (workflow mismatch between "vagrant vm >>> looping" and "ansible parallelism"). I thus opened >>> https://github.com/mitchellh/vagrant/pull/1723, which meets my needs by >>> generating on the fly a single-host inventory file for each VM to >>> provision. It is quite handy for playbook development (so far, I don't plan >>> to use vagrant for staging/prod site deployments). Of course this approach >>> does not support [host groups]. >>> >>> >> For me it's also a problem that the Vagrant Ansible plugin calls the >> provisioner separately for each VM. I'd also like it to be run once after >> all VMs are up, to take advantage of Ansible's parallelism. I opened an >> issue about this in Vagrant's tracker: >> >> https://github.com/mitchellh/vagrant/issues/1784 >> >> However, I don't think this issue should be mixed with the >> auto-generation of an inventory file by Vagrant (which is a separate >> feature request). For example, I use the inventory file to pass some >> variables, so an auto-generated one is not an option for me. >> >> -- >> 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:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > Michael DeHaan <[email protected] <javascript:>> > CTO, AnsibleWorks, Inc. > http://www.ansibleworks.com/ > >
-- 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/7d06c842-8ca4-41c0-9369-d0e0fda093b1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
