Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NFS synched folders and SL configuration #56

Open
lonniev opened this issue Apr 21, 2015 · 6 comments
Open

NFS synched folders and SL configuration #56

lonniev opened this issue Apr 21, 2015 · 6 comments

Comments

@lonniev
Copy link

lonniev commented Apr 21, 2015

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.)

@ju2wheels
Copy link
Contributor

@lonniev, can you please post a link to the section of the vagrant-libvirt you were comparing to vagrant-softlayer and ill review it later today.

@lonniev
Copy link
Author

lonniev commented Apr 21, 2015

https://github.com/audiolize/vagrant-softlayer/blob/master/lib/vagrant-softlayer/action/sync_folders.rb

Looking at what this is doing for rsync, I wonder if I am missing some config that would get the rsync choice to work. It looks like this code is attempting to pre-create the directories on the guest before rsyncing into them. So, why don't those directories exist when checked afterwards and why does rsync work for path-less copies but not for copies into multi-path directories?

@lonniev
Copy link
Author

lonniev commented Apr 21, 2015

Does the chef-solo provisioner not use the sync_folders code that the vagrant-softlayer provider offers? If so, that would suggest how rsync would work in one context but then fail in the next.

@lonniev
Copy link
Author

lonniev commented Apr 21, 2015

Conflating issues, the one I have with chef-solo is the same (I think) as hashicorp/vagrant#5255

@lonniev
Copy link
Author

lonniev commented Apr 21, 2015

Looks very much like getting pre-release Vagrant 1.7.3 would help me.

I currently install vagrant from the dmg at vagrantup.com; how does one get the pre-release installed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants