Can Fog be used without NFS?
-
Hi, I’m using Fog already a few years now. I’m pretty satisfied with it. The company was looking everything on the network now and they found my NFS share of fog. It’s open to anyone. They don’t like that. Is there a way of installing or reconfiguring Fog without using NFS at all?
-
@Pingolin Technically, yes, realistically probably not.
The reason we use NFS is due to speed and efficiency.
Is there a particular reason you cannot use NFS? Unless you’re using the FOG Server’s NFS to store other data from your company? FOG Server’s are not intended to be that way. The NFS is the point that allows sharing the images you capture and deploy to the machine’s your capturing/deploying (from/to).
NFS is the most user friendly way of accomplishing this.
Now there are past attempts to use SMB shares (Windows file sharing style) but it requires a lot more effort to stand up and is not necessarily guaranteed to work better and might not meet the requirements your company is wanting.
-
@Tom-Elliott This is what they told me: Just that the NFS mount that the server uses needs to be shared out to only this server, not shared out to everything.
But if I go to the /etc/exports and I put it like this:
/images 192.168.0.26(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0)
/images/dev 192.168.0.26(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)Now when I reboot a computer to and try to put an image one it it has no access. But that’s the point of using this NFS I guess. They don’t like it to be open to everyone. The fog server should have access to it and just push it to the computer or laptop I need to do but not working. Any suggestion how to solve this perhaps.
-
@Pingolin I believe you can setup the ip as subnets:
For example:
/images 192.168.0.0/24(ro,sync,no_wdelay,no_subtree_check,insecure_locks,no_root_squash,insecure,fsid=0) /images/dev 192.168.0.0/24(rw,async,no_wdelay,no_subtree_check,no_root_squash,insecure,fsid=1)Which would only allow 192.168.0 subnet to connect to the nfs share.
-
@Tom-Elliott Even that’s too much for them. They don’t want that NFS is sharing with nobody but without it, it’s impossible to run it I guess unless perhaps using the Samba protocol. Tried to install the latest version of Fog today but got stuk during install.
