-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
nfs-Ganesha integration #65
Comments
With this gluster/glusterfs#3745 enhancement in Gluster. Vol file server is available with every Storage Unit processes. No changes required from Kadalu Storage to export with NFS Ganesha. We need to package nfs-ganesha + gluster integration as nfs-ganesha-kadalu package to avoid mixing with Gluster versions.
|
Intial Observations on nfs-ganesha + moana
nfs-ganesha setup
|
Fix this issue for 1.0 release itself since changing this lator may need extra effort to handle in backward compatible way.
@amarts is it possible to add |
Should be possible to add volume-id in client volfile. |
NFS Ganesha integration worked! Little changes to the nfs-ganesha build steps(
One more dependency required was |
Updates: kadalu#65 Signed-off-by: Shree Vatsa N <vatsa@kadalu.tech>
Updates: kadalu#65 Signed-off-by: Shree Vatsa N <vatsa@kadalu.tech>
CLIs:
Above commands enable or disable the NFS Ganesha exports in any of the managed nodes. If Note: Do not start/restart nfs-ganesha service, only handle export and unexport of volumes. Another option to enable the NFS export locally (Outside the Storage cluster).
To enable:
To disable:
|
Ref: Gluster Hook script that enables the NFS ganesha service |
Updates: kadalu#65 Signed-off-by: Shree Vatsa N <vatsa@kadalu.tech>
Updates: #65 Signed-off-by: Shree Vatsa N <vatsa@kadalu.tech>
The text was updated successfully, but these errors were encountered: