Attempting to use NFS synched folders with a Mac OS host and Windows guests on Softlayer and after enabling the necessary NFS service within the Windows servers, I see that /etc/exports is not updated and that I get the error about no host IP address provided
Comparing the vagrant softlayer code with the vagrant libvirt code, I see that apparently it is the responsibility of the provider code to discover and set the nfs_host_ip and nfs_machine_ip environment variables--and that SL does not appear to do this.
If I'm right, can the vagrant softlayer documentation be updated to state that NFS support isn't available and can this issue be an enhancement request for that support?
If I'm wrong, what is the ordered set of configuration statements to get NFS support to work for vagrant softlayer?
(Why am I going through all this trouble? Because the chef-solo Windows code does not pre-create the full paths that the rsync folder sync requires and rsync errors out when attempting to sync the chef folders.)
Attempting to use NFS synched folders with a Mac OS host and Windows guests on Softlayer and after enabling the necessary NFS service within the Windows servers, I see that /etc/exports is not updated and that I get the error about no host IP address provided
Comparing the vagrant softlayer code with the vagrant libvirt code, I see that apparently it is the responsibility of the provider code to discover and set the nfs_host_ip and nfs_machine_ip environment variables--and that SL does not appear to do this.
If I'm right, can the vagrant softlayer documentation be updated to state that NFS support isn't available and can this issue be an enhancement request for that support?
If I'm wrong, what is the ordered set of configuration statements to get NFS support to work for vagrant softlayer?
(Why am I going through all this trouble? Because the chef-solo Windows code does not pre-create the full paths that the rsync folder sync requires and rsync errors out when attempting to sync the chef folders.)