Enhancements

This section describes the major enhancements introduced in IBM Storage Fusion Data Foundation 4.14.

Support for higher disk capacities and disk quantities

Previously, for local storage deployments IBM recommended 9 devices or less per node and disks size of 4 TiB or less. With this update, the recommended devices per node is now 12 or less, and disks size is 16 TiB or less.

Faster RWO recovery in case of node failures

Previously, it took a long time for Screenwriter (RWO) volumes to recover in case of node failures. With this update, node failures are automatically handled by the cluster once the appropriate taints are added to the node.

Taint node.kubernetes.io/out-of-service=nodeshutdown:NoExecute or node.kubernetes.io/out-of-service=nodeshutdown:NoSchedule is added to the node, and RWO volumes no longer take a long time to recover.

Automatic space reclaiming for RBD persistent volume claims PVCs

Fusion Data Foundation 4.14 introduces automatic space reclaiming for RBD persistent volume claims PVCs that are in the namespace that begins with openshift-. This means administrators no longer have to manually reclaim space for the RBD PVCs in the namespace that starts with openshift- prefix.

Automation of annotating encrypted RBD storage classes

Annotation is automatically set when the OpenShift console creates a RADOS block device (RBD) storage class with encryption enabled. This enables customer data integration (CDI) to use host-assisted cloning instead of the default smart cloning.

LSOs LocalVolumeSet and LocalVolumeDiscovery CRs now support mpath device types

With this release, disk and mpath device types are available for LocalVolumeSet and LocalVolumeDiscovery CRs.

Automatic detection of default StorageClass for OpenShift virtualization workloads

Fusion Data Foundation deployments using OpenShift Virtualization platform now have the default StorageClass automatically detected.

Collect rbd status details for all images*

When troubleshooting certain RBD related problems, the status of the RBD-images is an important piece of information. With this release, odf-must-gather includes the rbd status details, making it faster to troubleshoot RBD related problems.

Change in default permission and FSGroupPolicy

Permissions of newly created volumes now defaults to a more secure 755 instead of 777. FSGroupPolicy is now set to File to allow application access to volumes based on FSGroup. This involves Kubernetes using fsGroup to change permissions and ownership of the volume to match user requested fsGroup in the pod’s SecurityPolicy.

Note:

Existing volumes with a huge number of files may take a long time to mount since changing permissions and ownership takes a lot of time.