purpleidea/oh-my-vagrant

`--stdin` is not supported on Debian derivatives of `passwd` utility, use
another method to set root password.
Also if VM update requested - take this into account and call `apt-get` instead of
`yum`.

…ping for long lines; changed wording in :vms documentation section a bit

By default Vagrant runs Ansible provisioner limited to single host.
This prevents us to get facts from other hosts - which makes it
impossible to provision clustered environment with OMV and Ansible.

"ansible.limit = 'all'" resolves this.

Additionally, most of Ansible roles/playbooks are designed to be run
under 'root' system account. To avoid un-needed playbooks modifications
and adding "sudo: yes" here and there, we explicitly tell Vagrant to use
'root' when it runs Ansible provisioning.

… IP data inside the mainloop

… needed. VIP definitions/usage returned. As per James in #62, it should be there, and "It should be the same for all machines."

…xed tabbing

… VMs by supplying `config.vm.ip = '1.2.3.4'` parameter. Thus, with Libvirt DHCP disabled, and supplying own IPs to each VM, we can have a decent working setup. Furthermore, /etc/hosts approach is completely fine here for name resolving purposes - neither of other approaches provide a flexibility of a plain text file. With Vagrant We're not intended to build a working root DNS servers setup and put it to production anyways :)