Bug #46492
closed
mgr/dashboard: adapt NFS-Ganesha design change in Octopus (daemons -> services)
Added by Kiefer Chang almost 4 years ago.
Updated about 3 years ago.
Description
Starts from Octopus release, Ganesha daemons deployed by Cephadm or Volumes NFS interface shared a single configuration RADOS object.
This change deprecates the usage in previous releases.
See this URL for how we advised to config nfs-ganesha settings for the Dashboard before.
See this URL for the design change.
To adapt the change, we need to
- Revise the design in NFS page. Daemons in the exports should be changed to `Service`.
- Revise the DOC (1) Providing new configuration guidelines (2) How to migrate old exports.
- Subject changed from mgr/dashboard: adapt NFS-Ganesha desing change in Octopus (daemons -> services) to mgr/dashboard: adapt NFS-Ganesha designg change in Octopus (daemons -> services)
- Subject changed from mgr/dashboard: adapt NFS-Ganesha designg change in Octopus (daemons -> services) to mgr/dashboard: adapt NFS-Ganesha design change in Octopus (daemons -> services)
- Category changed from 144 to API Tests
- Related to Bug #46327: cephadm: nfs daemons share the same config object added
- Category changed from API Tests to 144
- Status changed from New to In Progress
- Assignee set to Kiefer Chang
- Pull request ID set to 36948
- Related to Feature #47490: Integration of dashboard with volume/nfs module added
- Status changed from In Progress to Pending Backport
- Target version set to v16.0.0
- Copied to Backport #47944: octopus: mgr/dashboard: adapt NFS-Ganesha design change in Octopus (daemons -> services) added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
- Project changed from mgr to Dashboard
- Category changed from 144 to Component - NFS
Also available in: Atom
PDF