Assignment 3: NFSv4 client

Configuration and checking of frontend VM as a NFSv4 client

Now it is time to configure the frontend VM as a NFSv4 client:

1. Pre-Installation: As with server-03, make sure to configure frontend as client of service supplied by server-01 (lab 1):

   • NTP client. Time (date) of our file server should be automatically synchronized by the NTP service. Use the ntp package and configure it in the same way as server-03.

   • DNS client. Add server-01 as secondary DNS for your server.

   • LDAP client. Our new server will be able to use the LDAP directory in a safe way (SSL) to identify and authenticate users who are managed by LDAP on server-01/server-02.

     • Configure frontend as LDAP client host so that we can access the LDAP directory using the LDAP client Command utility (ldapserach, ldapadd, ldapmodify …). Remember that the connection must be secure, over SSL and that we have a replicated LDAP system.

     • Add LDAP services on server-01/server-02 as user/host identification method.

     • Reconfigure the client system to enable LDAP authentication for the SSH service.

2. Installation: First, we must install and pre-configure the NFS client "side":

   • nfs-common

3. NFSv4 configuration on frontend:

   • NFS static configuration. Configure the frontend VM to enable the initial static mount (booting time) of /export/scratch (server-03) on /remote/scratch (frontend) over NFS. Ensure this is done permanently. Consider the default mount options.

   • NFS dynamic (automount) configuration. Now, configure the frontend VM to mount dynamically (on demand) over NFS on the local directory /remote/home/ , the user HOME directories copied to the remote directory /export/home/, located on server-03:

     • Mount options:

       1. acl

4. Operation checking:

   • After login tofrontendas regular user (user/user2), the /remote/scratch directory must be mounted automatically .

     • One LDAP user (user2) will be able to open an SSH session on frontend, and also have its $HOME directory (located on server-03) available. That directory will be mounted on demand and automatically.

     • On frontend, check the default “acls” for user2 $HOME:

       • Check that the changes made to the previous module are maintained:

         1. For “user1”, allow TOTAL access to user2 $HOME.

         2. For “user2”, deny TOTAL access to user1 $HOME.

More details in references [4][5]

1. Verify that the quota system operates properly.

   • Login as user2 and create a file image of size 1024 MB. Use the dd command.

pageReferences and Resources