mgr/volumes/nfs: Add interface for adding user defined configuration#36351
mgr/volumes/nfs: Add interface for adding user defined configuration#36351batrick merged 3 commits intoceph:masterfrom
Conversation
|
Depends on PR #36338 |
|
cc @BlaineEXE |
ec5d652 to
dc0cd42
Compare
dc0cd42 to
ca18d0f
Compare
|
With Rook (and I think cephadm) I am thinking about the workflow that will be used programmatically by the orchestrator. In my mind, thinking of Rook, it looks something like below.
The biggest question I am left with after looking at this draft PR is whether the user must re-specify the minimal connection configs from my item 1 in order to apply config changes or whether applying config changes will "merge" with the Rook-applied minimal configs. |
Code related to creating and removing rados object has been rearranged abd modified. This patch introduces interface to set and reset user config. nfs cluster config set <clusterid> -i <config_file> nfs cluster config reset <clusterid> Fixes: https://tracker.ceph.com/issues/45747 Signed-off-by: Varsha Rao <varao@redhat.com>
Signed-off-by: Varsha Rao <varao@redhat.com>
Signed-off-by: Varsha Rao <varao@redhat.com>
ca18d0f to
bba2d66
Compare
User will not be required to respecify the default/minimal config again. As Ganesha uses the last loaded config block. |
Set config command saves the user defined config in rados object, adds it's url to common config and restarts the ganesha service.
Reset config command deletes the user defined config object, removes url from common config and restarts the ganesha service.
Fixes: https://tracker.ceph.com/issues/45747
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 dashboard backendjenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume tox