Ceph » ceph-ansible

The cephadm generated ganesha.conf differs from what manila uses because there's no flexibility in configuring different options other than [1].
The Openstack ganesha config used for manila was generated by ceph-ansible through [2].
The ganesha config produced by the nfs cephadm deployed daemon breaks the backward compatibility with the ceph-ansible generated one.
For this reason, even though issue [3] is solved, we won't still be able to properly configure the Manila project with Ceph.

Here an example of the config produced by ceph-ansible:

NFS_Core_Param
{
           Bind_Addr={{ IP_ADDRESS }};
    }
    EXPORT_DEFAULTS {
            Attr_Expiration_Time = 0;
    }
    CACHEINODE {
            Dir_Chunk = 0;
            NParts = 1;
            Cache_Size = 1;
    }
    RADOS_URLS {
       ceph_conf = '/etc/ceph/ceph.conf';
       userid = "manila";
    }
    %url rados://manila_data/ganesha-export-index
    NFSv4 {
            RecoveryBackend = 'rados_kv';
    }
    RADOS_KV {
            ceph_conf = '/etc/ceph/ceph.conf';
            userid = "manila";
            pool = "manila_data";
    }     
    LOG {
            Facility {
                    name = FILE;
                    destination = "/var/log/ganesha/ganesha.log";
                    enable = active;
            }  
    }

[1] https://github.com/ceph/ceph/blob/master/src/pybind/mgr/cephadm/templates/services/nfs/ganesha.conf.j2
[2] https://github.com/ceph/ceph-ansible/blob/master/roles/ceph-nfs/templates/ganesha.conf.j2
[3] https://tracker.ceph.com/issues/50360