mgr/volumes/nfs: remove 'ganesha-' prefix from cluster id#38510
mgr/volumes/nfs: remove 'ganesha-' prefix from cluster id#38510batrick merged 2 commits intoceph:masterfrom
Conversation
batrick
left a comment
There was a problem hiding this comment.
I'm okay with this change but what about making it backwards compatible for folks who setup clusters on Octopus?
This PR[1] in volume nfs plugin will remove it too. Since it can cause inconsistencies. [1] ceph/ceph#38510 Signed-off-by: Varsha Rao <varao@redhat.com>
The way namespace is set, makes backward compatibility complicated. |
|
jenkins retest this please |
This PR[1] in volume nfs plugin will remove it too. Since it can cause inconsistencies. [1] ceph/ceph#38510 Signed-off-by: Varsha Rao <varao@redhat.com>
PR[1] in volume nfs plugin will remove it too. Since it can cause inconsistencies. This change will not affect exports created using dashboard. As it looks for ganesha config object just by 'conf-' [2]. Exports cannot be created by using volume/nfs plugin in Octopus version. Because the ceph rook module is broken. [1] ceph/ceph#38510 [2] https://github.com/ceph/ceph/blob/octopus/src/pybind/mgr/dashboard/services/ganesha.py#L1111 Signed-off-by: Varsha Rao <varao@redhat.com>
PR[1] in volume nfs plugin will remove it too. Since it can cause inconsistencies. This change will not affect exports created using dashboard. As it looks for ganesha config object just by 'conf-' [2]. Exports cannot be created by using volume/nfs plugin in Octopus version. Because the ceph rook module is broken. [1] ceph/ceph#38510 [2] https://github.com/ceph/ceph/blob/octopus/src/pybind/mgr/dashboard/services/ganesha.py#L1111 Signed-off-by: Varsha Rao <varao@redhat.com>
PR[1] in volume nfs plugin will remove it too. Since it can cause inconsistencies. This change will not affect exports created using dashboard. As it looks for ganesha config object just by 'conf-' [2]. Exports cannot be created by using volume/nfs plugin in Octopus version. Because the ceph rook module is broken. [1] ceph/ceph#38510 [2] https://github.com/ceph/ceph/blob/octopus/src/pybind/mgr/dashboard/services/ganesha.py#L1111 Signed-off-by: Varsha Rao <varao@redhat.com>
I think the most basic form of backwards compatibility is to just load |
744947b to
abd6894
Compare
As per discussion change to config object is not required to maintain backward compatibility. Rather will require changes to namespace. |
Orchestrator defines service name as "<service_type>.<service_id>". The ganesha common config object name in orchestrator is "conf-<service_name>". Volume's nfs plugin deploys nfs-ganesha clusters with 'ganesha' prefixed to cluster id and common config object. It can cause unecessary issues in rook and cephadm. So let's remove the prefix. Fixes: https://tracker.ceph.com/issues/48514 Signed-off-by: Varsha Rao <varao@redhat.com>
Signed-off-by: Varsha Rao <varao@redhat.com>
abd6894 to
ef3660b
Compare
The nfs-ganesha cluster name was recently updated in this PR[1]. Update the nfs service id to maintain uniformity. [1] ceph#38510 Fixes: https://tracker.ceph.com/issues/49121 Signed-off-by: Varsha Rao <varao@redhat.com>
The nfs-ganesha cluster name was recently updated in this PR[1]. Update the nfs service id to maintain uniformity. [1] ceph#38510 Fixes: https://tracker.ceph.com/issues/49121 Signed-off-by: Varsha Rao <varao@redhat.com>
The nfs-ganesha cluster name was recently updated in this PR[1]. Update the nfs service id to maintain uniformity. [1] ceph#38510 Fixes: https://tracker.ceph.com/issues/49121 Signed-off-by: Varsha Rao <varao@redhat.com> (cherry picked from commit f0969ce)
The nfs-ganesha cluster name was recently updated in this PR[1]. Update the nfs service id to maintain uniformity. [1] ceph#38510 Fixes: https://tracker.ceph.com/issues/49121 Signed-off-by: Varsha Rao <varao@redhat.com> (cherry picked from commit f0969ce)
The nfs-ganesha cluster name was recently updated in this PR[1]. Update the nfs service id to maintain uniformity. [1] ceph#38510 Fixes: https://tracker.ceph.com/issues/49121 Signed-off-by: Varsha Rao <varao@redhat.com>
Orchestrator defines service name as "<service_type>.<service_id>". The ganesha
common config object name in orchestrator is "conf-<service_name>". Volume's
nfs plugin deploys nfs-ganesha clusters with 'ganesha' prefixed to cluster id
and common config object. It can cause unecessary issues with rook and cephadm
nfs deployments. So let's remove the prefix.
Fixes: https://tracker.ceph.com/issues/48514
Signed-off-by: Varsha Rao varao@redhat.com
Note: Not supporting backward compatibility
Show available Jenkins commands
jenkins retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume tox