I've been reading the Vagrant docs and there's one non-critical issue that's got me wondering. That is, by what means does Vagrant communicate with the VMs in order to do provisioning? I'm guessing it's through ssh because I can't think of anything else it could be.
Assuming this is true, then it also has to be true that Vagrant includes Ruby code that can do the data transfer part of ssh. This is because Vagrant works on Windows but Windows doesn't include ssh out of the box.
I think a short mention of how this works would be useful in the Vagrant docs.
"During this method, the provisioner should SSH and run any commands it requires for provisioning"
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/groups/opt_out.
It is SSH. This is being abstracted away in a future version though. Provisioners should just assume they have a shell. The method by which their commands are carried out should be of no concern (from an implementation perspective). This leads the way for things such as direct guest execution (via VirtualBox's API) or WinRM and such possible.