As per subject line, we will be deprecating the standalone CephFS NFS protocol helper in this cycle.
This is following our deprecation warning we put out in 2024.1 / Caracal [1] [2].
We've supported using a clustered Ceph NFS service since the Zed release.
We've also added upgrade helpers to migrate from a standalone NFS-Ganesha service to the ceph-orch-deployed clustered NFS service; this code was backported to stable/2023.1 (Antelope).
Although the upgrade path is disruptive, there is a UX improvement in Manila to ease this migration through surfacing “preferred” export paths.
Moving forward, deployments must have “cephfs_nfs_cluster_id” in your configuration, otherwise the driver will fail to start.
Manila will not make any export changes to NFS-Ganesha, so upgrading manila without an NFS cluster will mean that only the control plane is not going to work; but, data plane will remain unaffected.
To assist migration, admins can also configure "cephfs_ganesha_export_ips" (or alternatively, "cephfs_ganesha_server_ip") alongside "cephfs_nfs_cluster_id".
Setting these options will allow the CephFS driver to report additional export paths. These additional export paths will have the "preferred" metadata key set to False.
Best,
Manila team
[1]
https://review.opendev.org/c/openstack/manila/+/912648 [2]
https://docs.openstack.org/manila/2024.2/configuration/shared-file-systems/drivers/cephfs_driver.html#for-cephfs-nfs-shares