NFS Options for Private Cloud

Cloudera Machine Learning Cloudera Private Cloud requires a Network File System (NFS) server for storing project files and folders.

On Cloudera Embedded Container Service, NFS is part of the overall installation, and no additional setup steps are required.

You can use an NFS server that is external to the cluster, such as a NetApp Filer appliance. In this case, you must manually create a directory for each workspace. In this case, the NFS server must be configured before deploying the first Cloudera Machine Learning Workspace in the cluster. One important limitation is that Cloudera Machine Learning does not support using shared volumes for storing project files.

Storage provisioner change On OCP, CephFS is used as the underlying storage provisioner for any new internal workspace on Cloudera Private Cloud 1.5.1. A storage class named ocs-storagecluster-cephfs with CSI driver set to openshift-storage.cephfs.csi.ceph.com must exist in the cluster for new internal workspaces to get provisioned. Each workspace will have separate 1 TB internal storage.

On Cloudera Embedded Container Service, any new internal workspace on 1.5.1 will use Longhorn as the underlying storage provisioner. A storage class named longhorn with CSI driver set to driver.longhorn.io must exist in the cluster for new internal workspaces to get provisioned. Each workspace will have separate 1 TB internal storage.

On either Cloudera Embedded Container Service or OCP, internal workspaces running on Cloudera Private Cloud 1.4.0/1.4.1 use NFS server provisioner as the storage provisioner. These workspaces when upgraded to 1.5.0 will continue to run with the same NFS server Provisioner. However, NFS server provisioner is now deprecated and is not supported in the 1.5.1 release.