[Container-tools] Query on mounted volumes being inaccessible between host and guest - ADB Issue #118 (Blocker)

[Shubham Minglani]

----- Original Message -----
> From: "Max Rydahl Andersen" <manderse at redhat.com>
> To: "Shubham Minglani" <sminglan at redhat.com>
> Cc: container-tools at redhat.com
> Sent: Friday, February 12, 2016 11:21:23 PM
> Subject: Re: [Container-tools] Query on mounted volumes being inaccessible between host and guest - ADB Issue #118
> (Blocker)

> > Solution 1 - SSHFS (vagrant-sshfs plugin) (testing in progress)
> >
> > Pros:
> > - One solution for all platforms
> >
> > Cons:
> > - No longer maintained, so it has to be maintained by us since it
> > might break with future Vagrant versions
> > - Performance issues (high latency, reliable over heavy load?) since
> > it's working over SSH
> > - SSH server has to be packaged with the Windows installer
> 
> How is security handled here ? how is the vagrant box able to connect to
> the host ? do users need to configure
> username/passwords ?

Saleem is testing SSHFS, so he might have the answers to these.

> > Solution 2 - NFS (Linux + Mac) and SMB (Windows)
> >
> > https://www.vagrantup.com/docs/synced-folders/nfs.html
> > https://www.vagrantup.com/docs/synced-folders/smb.html
> >
> > Pros:
> > - Maintained by Vagrant, so easier to maintain. Also, this will have
> > more testing and user feedback backing it than our customized
> > vagrant-sshfs plugin will have.
> > - Works out of the box, just one `vagrant up`
> > - No tinkering required on the Windows host (but NFS server required
> > on Linux and Mac hosts)
> 
> Mac has smb built in afaik. don't know about NFS - but if users need to
> install it this feels doomed since
> we already have a ton of other things that need to be configured.

Vagrant configures everything on the host, be it SMB or NFS, no configuration required.

> > Steps for Windows:
> > - `vagrant up`
> > - `vagrant provision`
> > - `vagrant reload`
> >
> > Steps for Linux:
> > - Allow incoming connections to the NFS server on the host
> > - `vagrant up`
> 
> I'm not following why the steps are different between the OS's here ?
> 
> And if users need to learn to run all three vagrant up/provision/reload
> and different between OS's this is bad/not good either ;/

There is only one step i.e. `vagrant up`, the extra ones are there because cifs-utils has not been packaged in adb vagrant box, yet!

Thanks for your input,
Regards,
Shubham