You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I have been trying to get started by making my own base VM that vagrant will clone to use to provision hosts and I am looking to see how Vagrant can configure the network on these hosts. Ideally, I would want to be able to assign IPs to these hosts in the Vagrantfile and have them join an existing network. Is this possible or must I completely rely on what is set up in the image? Is there a way to make Vagrant "see" into the guest OS? That is kind of essential since the goal here is to be able to provision these instances with chef.
The text was updated successfully, but these errors were encountered:
I believe there is a way for Vagrant to set the IP of the VM. The provider is calling the CloneVM_Task method in the vSphere API. One of the arguments to this method is a VirtualMachineCloneSpec object. I think setting the customization.nicSettingMap.adapter.ip property to a CustomizationFixedIP object will do the trick. See http://pubs.vmware.com/vsphere-50/index.jsp#com.vmware.wssdk.apiref.doc_50/vim.vm.CloneSpec.html.
This kind of configuration is not currently supported by the provider but could be added. We've been relying on dynamically assigned IP addresses. Vagrant stores the VM's UUID which we are using to get the IP for SSH.
Hi, I have been trying to get started by making my own base VM that vagrant will clone to use to provision hosts and I am looking to see how Vagrant can configure the network on these hosts. Ideally, I would want to be able to assign IPs to these hosts in the Vagrantfile and have them join an existing network. Is this possible or must I completely rely on what is set up in the image? Is there a way to make Vagrant "see" into the guest OS? That is kind of essential since the goal here is to be able to provision these instances with chef.
The text was updated successfully, but these errors were encountered: