Use the vagrant-winrm Vagrant plugin to resolve VM IP address. #155
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It turns out that the IP address of the Vagrant VM returned by the
`vagrant ssh-config` varies with each Vagrant provider and so can't be
relied on to return a private/nat'ed address. In some cases
`"127.0.0.1"` is returned and the locally forward port is returned for
the port number.
To resolve this, the `vagrant-winrm` Vagrant plugin will be used,
exposing a `vagrant winrm-config` subcommand to return WinRM-specific
connection details of the form:
Host CustomHostname
HostName Windows2008VM.vagrant.up
Port 5985
User vagrant
Password vagrant
This plugin requires version 1.6 of Vagrant or higher and this Driver
will check to see that the plugin is installed and the Vagrant version
is sufficient--if not a UserError is raised with a message describing
what action(s) to take.
If a WinRM transport is not used, then the minimum version of Vagrant
remains 1.1.0 (as before) and the `vagrant-winrm` plugin will not be
required keeping a slimer set of requirements for users who don't care
to manage Windows VMs.
For more details about the `vagrant-winrm` plugin, please see:
https://github.com/criteo/vagrant-winrm
Closes #153
fnichol
added a commit
that referenced
this pull request
Mar 26, 2015
Use the vagrant-winrm Vagrant plugin to resolve VM IP address.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It turns out that the IP address of the Vagrant VM returned by the
vagrant ssh-configvaries with each Vagrant provider and so can't berelied on to return a private/nat'ed address. In some cases
"127.0.0.1"is returned and the locally forward port is returned forthe port number.
To resolve this, the
vagrant-winrmVagrant plugin will be used,exposing a
vagrant winrm-configsubcommand to return WinRM-specificconnection details of the form:
This plugin requires version 1.6 of Vagrant or higher and this Driver
will check to see that the plugin is installed and the Vagrant version
is sufficient--if not a UserError is raised with a message describing
what action(s) to take.
If a WinRM transport is not used, then the minimum version of Vagrant
remains 1.1.0 (as before) and the
vagrant-winrmplugin will not berequired keeping a slimer set of requirements for users who don't care
to manage Windows VMs.
For more details about the
vagrant-winrmplugin, please see:https://github.com/criteo/vagrant-winrm
Closes #153