For single machine, Vagrant's built in ansible provisioner is good.  For 
multi-machine, you could consider using the dynamic inventory (slooow), or 
better, just source a configuration file (json, yaml, csv, ini, whatever) 
from the Vagrantfile and from a dynamic inventory.

I created some example scenarios where, Vagrant, Shell Scripts, and Ansible 
dynamic inventory from a config file (one source of truth):

   - https://bitbucket.org/jmenchaca/vagrant-simple 

The only draw back, is that it doesn't reflect current state of the systems 
(that they are running), only that they are configured to run, and how to 
access them through Vagrant's private key.


-- 
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/5e69e460-3adf-4469-a53d-7ee89aec3a7b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to