Description of problem: This request is similar to that in https://bugzilla.redhat.com/show_bug.cgi?id=1925646 and originates from Red Hat OpenStack's use of nfs-ganesha to provide CephFS shares via an NFS gateway for multi-tenant clouds. Currently, there are a set of sensible default configuration options in the nfs-ganesha template in ceph-ansible via a ganesha jinja template [1]. Customers would like to update client related configuration in NFS_CORE_PARAM and metadata caching related options within MDCACHE blocks based on the kind of workloads they wish to run. It would be more flexible if ceph-ansible would allow overriding these values or provide a way to point to an alternative jinja template file [2] that could be used during deployment. Additional info: [1] https://github.com/ceph/ceph-ansible/blob/a7f2fa73e63e69dba2e41aaac9732397eec437c9/roles/ceph-nfs/templates/ganesha.conf.j2 [2] https://github.com/ceph/ceph-ansible/blob/a7f2fa73e63e69dba2e41aaac9732397eec437c9/roles/ceph-nfs/tasks/start_nfs.yml#L43
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Red Hat Ceph Storage 4.3 Security and Bug Fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:1716
Currently ceph‑ansible ships a fixed nfs‑ganesha template with default NFS_CORE_PARAM and MDCACHE values, but customers need flexibility to tune these for different workloads. Allowing overrides or pointing to a custom Jinja template during deployment would make configuration more adaptable and better suited to varied use cases. https://www.ez-passnc.com