Accessing remote IBM Storage Scale storage cluster in IBM Storage Fusion
You can configure a remote file system mount for IBM Storage Scale and access it.
About this task
Note: The Global Data Platform remote
mount capability is available only for the following deployment modes:
- Standalone rack with Global Data Platform (newly installed IBM Storage Fusion 2.8.x that is compliant with network requirements and upgraded to IBM Storage Fusion 2.8.0 with OpenShift® Container Platform 4.15. For more information about the network requirements, see Planning and prerequisites for remote mount support.
- Standalone rack with FDF ( upgraded to IBM Storage Fusion 2.8.0 / newly installed with IBM Storage Fusion 2.8.x)
- Expansion multirack with Global Data Platform storage (newly installed with IBM Storage Fusion 2.8.1)
You can run a container workload against an existing data set that is stored on an IBM Storage Scale file system. For example, an IBM Storage Scale file system contains lot of images and you want to run a container workload that specializes in image processing.
- The remote file system mount must be configured. For more information, see Connecting to remote IBM Storage Scale file systems.
- When the remote file system mount is created, the IBM Storage Fusion automatically creates a statically provisioned volume that points to the file system. You must know how to identify this Persistent Volume.
- Optionally, modify the file system path that is specified in the Persistent Volume so that it points to a specific directory in the file system, rather than the root.
- Now a Persistent Volume Claim (PVC) can be made against the Persistent Volume. It can be
accomplished by matching the
accessMode
and storage request against the specified in the Persistent Volume. - A workload that uses the Persistent Volume Claim can view the contents of the file system.
Configure the UID/GID to match the one that is used to write the data set on the IBM Storage Scale file system. If you do not configure, then the container workload cannot access the files, because it does not have the permission.