Setting up NFS storage

If you plan to use NFS for persistent storage, you must set up your NFS storage before you install IBM® Software Hub.

Installation phase
  • You are not here. Setting up a client workstation
  • You are not here. Setting up a cluster
  • You are not here. Collecting required information
  • You are not here. Preparing to run installs in a restricted network
  • You are not here. Preparing to run installs from a private container registry
  • You are here icon. Preparing the cluster for IBM Software Hub
  • You are not here. Preparing to install an instance of IBM Software Hub
  • You are not here. Installing an instance of IBM Software Hub
  • You are not here. Setting up the control plane
  • You are not here. Installing solutions and services
Who needs to complete this task?

Cluster administrator A cluster administrator or a storage administrator must complete this task.

When do you need to complete this task?

One-time setup If you plan to use NFS for persistent storage, you must complete the appropriate tasks for your environment.

It is highly recommended that your NFS storage is served by an enterprise class storage system that ensures availability with a sufficiently high throughput and reduced latency. It is recommended that the storage is in close proximity to the cluster. For example, the storage should be in the same network as the cluster. For details, see Disk requirements.

Ensure that the following statements are true on all the nodes you plan to run IBM Software Hub on:

  • All of the nodes in the cluster have access to mount the NFS server.
  • All of the nodes in the cluster have read/write access to the NFS server.
  • Containerized processes have read/write access to the NFS server.
    Important: Containerized processes create files that are owned by various UIDs. (In IBM Software Hub, most services use long UIDs between 1000320900 and 1000361000, as an example. UID range is decided by OpenShift® and project namespaces.) Db2 reserves a specific UID range because it uses a custom security context constraint (SCC). For more information, see Basic security features on. If you restrict access to the NFS served to specific UIDs, you might encounter errors when installing or running IBM Software Hub.

Before you begin

Determine which services you will install on IBM Software Hub.

At a minimum, you must configure dynamic provisioning for NFS storage.

However, if you plan to install any of the following services, which have a dependency on Db2U, you must also configure the NFS export options on your NFS server:
  • Data Product Hub
  • Data Virtualization
  • Db2
  • Db2 Big SQL
  • Db2 Warehouse
  • IBM Knowledge Catalog
  • IBM Knowledge Catalog Premium
  • IBM Knowledge Catalog Standard
  • IBM Manta Data Lineage
  • OpenPages (with an internal database)
  • watsonx.governance™ Risk and Compliance Foundation (with an internal database)

In addition, if you are running SELinux on your worker nodes, you might need to create an SELinux policy module on your worker nodes.

Use the following information to ensure that you complete the appropriate tasks for setting up your NFS storage:

Options What to do
I am installing a service that has a dependency on Db2U
  1. Configuring your NFS server
  2. Creating an SELinux policy module on Red Hat OpenShift worker nodes
  3. Setting up dynamic provisioning
I am not installing any services that have a dependency on Db2U, but I plan to install the privileged monitoring service.
  1. Configuring your NFS server
  2. Setting up dynamic provisioning
I am not installing any services that have a dependency on Db2U and I do not plan to install the privileged monitoring service.
  1. Setting up dynamic provisioning