Configuring your NFS server

If you are installing services that depend on Db2U on Cloud Pak for Data, you must configure the NFS export options and enable no_root_squash before you set up dynamic provisioning.

About this task

The following services have specific configuration requirements when setting up your NFS server:

  • Db2®
  • Db2 Big SQL
  • Db2 Warehouse
  • OpenPages® (with an internal database)
  • Watson™ Knowledge Catalog
  • Watson Query

Enabling no_root_squash allows root clients to retain root permissions on the remote NFS share. If you do not configure no_root_squash before installing your services, the Db2U instance will fail.

A Network Attached Storage (NAS) or Network File System (NFS) share must be exported to all NFS clients by using the following export options: rw, sync, no_root_squash, no_all_squash.

You must export the NFS mount to each of the Red Hat® OpenShift® worker nodes that host your service.

Procedure

  1. Run a command similar to the following example: 
    echo "/nfsmount db2_openshiftworker1_IP_address(rw,sync,no_root_squash,no_all_squash) db2_openshiftworker2_IP_address(rw,sync,no_root_squash,no_all_squash)" > /etc/exports

    Where db2_openshiftworker_IP_address is repeated for each worker node.

  2. Run the exportfs -a or exportfs -r command if a NAS controller is used to ensure that the newly added NFS shares are broadcast to the defined client list.