Hi
Not a flame war. I'm going to have a use case, where I spin up a lot of cloud VM. The worker VM does some work, and then returns the resulting work/files to a single VM. I'm looking at doing a NFS/Samba server for the storage VM. Any thoughts one way or the other.
The storage VM will be accessible from the client VMs. I'm assuming the client VM would mount the storage VM, and do some sort of write to the device.
The overall process would also have to employ selinux on both the client, as well as the storage VM.
Thoughts/Comments??
thanks
On 4/14/20 8:58 AM, bruce wrote:
Not a flame war. I'm going to have a use case, where I spin up a lot of cloud VM. The worker VM does some work, and then returns the resulting work/files to a single VM. I'm looking at doing a NFS/Samba server for the storage VM. Any thoughts one way or the other.
The storage VM will be accessible from the client VMs. I'm assuming the client VM would mount the storage VM, and do some sort of write to the device.
If the clients are all Linux, then you definitely want nfs. It's a native Unix filesystem which supports everything and is easy to setup. Samba is like a translation layer with potential mismatches on both side and will be a lot harder to get configured correctly.
On Tue, 14 Apr 2020 10:04:03 -0700 Samuel Sieb wrote:
Samba ... will be a lot harder to get configured correctly.
I can vouch for that. Once the security freaks removed public shares, it took me something like three years to wait for google searches to catch up to new samba and finally tell me how to get read/write access without a password. I mean who wouldn't find it obvious that the key config line is "map to guest = Bad User"?