Feature request for FOG 1.6.x - Configure image capture to use NFSv4 instead of NFSv3

  • Moderator

    @george1421 I’ve worked with nfsv4 for about a week now. Many times I’ve stopped in irritation that the system doesn’t work like the examples but I’ve finally have a solid configuration for NFSv4. While nfsv4 is nfs, its very different in its setup than versions of NFS less than v4. NFSv4 creates a logical file system that doesn’t necessarily align with the physical file system on the server. In some ways it makes things more complex, in other ways it allows for some pretty cool redirection.

    I’ve spent about 5 evenings trying to figure out how to map our current directory structure over to the nfsv4 file system. The problem was what ever the root was shared as ro or wr the child directories shares followed what the root share permissions were and ignored the specific share level permissions that the directories were exported as. I won’t go into details on the tests, but lets say I just ignored what I thought I knew and followed the examples and it worked.
    ref: https://cwiki.apache.org/confluence/display/DIRxINTEROP/NFSv4+Server+Export+Setup

    Just to repeat it again, nfsv4 creates a logical file system with the root of the share, what you define as the root directory in your exportfs. You only assign the fsid=0 what you are calling the root of your logical file system. For my example I’ve created the logical file system structure under /opt/fog/data directory. In this example I’ve created bind mounts to the original FOG directories to maintain backwards compatibility.

    Build the nfsv4 mount points

    mkdir -p /opt/fog/data/capture
    mkdir -p /opt/fog/data/images

    Freebie: so we present the same postinitscript files for both capture and imaging.

    mkdir -p /images/dev/postinitscripts
    mkdir -p /images/postinitscripts

    Create the bind loop back directories to map the physical file locations to the nfsv4 logical file system. Note this mapping can bring in directories from random locations but present them as a unified logical filesystem in NFS. This is the part that had me stuck for several days, where I thought I new better and this was unnecessary. But without this bind mount the child directories took on the share level permission of the logical nfs root.

    -> /etc/fstab
    /images/dev    /opt/fog/data/capture            none    bind 0 0
    /images        /opt/fog/data/images             none    bind 0 0
    /images/postinitscripts  /images/dev/postinitscripts   none    bind 0 0

    Just a placeholder for when creating the fogproject user. I would recommend that the fog installer actually set a unique user and group IP when the fog project user is created. Then we can use only the squash root to assign the files created by the root user to the unique group and user ID. Its really only adding security through obscurity so I did not add it into the install instructions here.

    We’ll add the fogproject user

    adduser fogproject

    Then we will grab the uid and gid of the fogproject user to use in the script that adds the nfs exports

    $uid = `grep fogproject /etc/passwd | cut -d ":" -f3`
    $gid = `grep fogproject /etc/passwd | cut -d ":" -f4`

    I’m only showing the product of the exports file not how $uid and $gid is set in the file
    -> /etc/exports

    /opt/fog/data/ *(fsid=0,no_subtree_check,crossmnt,all_squash,insecure,anonuid=1000,anongid=1000)
    /opt/fog/data/capture *(rw,sync,no_subtree_check,no_wdelay,no_subtree_check,insecure_locks,all_squash,insecure,anonuid=1000,anongid=1000)
    /opt/fog/data/images *(ro,sync,no_subtree_check,all_squash,insecure,anonuid=1000,anongid=1000)

    I understand the above is a big changed from what we have before. All users that connect to the nfs share will be squash all users to the fogproject user. The locks are only needed on a writeable share

    To configure the nfs server to only honor nfsv4 requests the following file needs to be edited
    -> /etc/nfs.conf


    Once the services are restarted the NFSv4 service will only accept nfs connects on tcp port 2049 where we can craft a custom firewall rule to protect without opening a large number of ports just for NFS.

    There will be some changes needed in the FOS linux OS to accommodate this new NFSv4 structure. Most notably is to update the mount command to send the connect request

    To capture an image

    mount -t nfs -o nfsvers=4,rw /mnt/images

    To deploy an image

    mount -t nfs -o nfsvers=4,rw /mnt/images

    As a side note you can connect to the nfs root directory with this

    mount -t nfs -o nfsvers=4,rw /mnt/images

    And then move between the logical shares. The nfsv4 root share is exported as ro. When you change into the capture share with cd the share permissions automatically change to rw. If you cd to /images the share permissions switch to ro. If you cd up one directory the change to ro.

    This is what a you see when you execute these commands.

    # mount -t nfs -o nfsvers=4,rw /mnt/images
    # cd images/
    # ls -la
    total 0
    drwxr-xr-x. 4 root  root 35 Dec  4 17:44 .
    drwxr-xr-x. 3 root  root 20 Nov 30 18:49 ..
    drwxrwxrwx. 3 fogproject fogproject 85 Dec  4 17:52 capture
    drwxrwxrwx. 5 fogproject fogproject 82 Nov 29 12:05 images

    Traversing these directory will change the share level permissions.

    I’m still working on the ARM project so now I’ll update the FOS Linux client with this new file structure to see how well (if) it works.

  • Moderator

    There is a nice article on how to setup NFSv4 with a single port open: https://peteris.rocks/blog/nfs4-single-port/