From fdd4ad287ef84b9179a5e9a38c130dab1c963661 Mon Sep 17 00:00:00 2001 From: Varsha Rao Date: Thu, 16 Jul 2020 17:06:11 +0530 Subject: [PATCH] doc/cephfs/nfs: Update about deploying nfs-ganesha with cephadm in vstart Fixes: https://tracker.ceph.com/issues/46571 Signed-off-by: Varsha Rao (cherry picked from commit 7f911a710d0fff7afab467f8c8216e3bdbff40b7) --- doc/cephfs/fs-nfs-exports.rst | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/doc/cephfs/fs-nfs-exports.rst b/doc/cephfs/fs-nfs-exports.rst index f35dae3f21d84..e2258b2ed8852 100644 --- a/doc/cephfs/fs-nfs-exports.rst +++ b/doc/cephfs/fs-nfs-exports.rst @@ -104,11 +104,24 @@ It displays export block for a cluster based on pseudo root name (binding). Configuring NFS-Ganesha to export CephFS with vstart ==================================================== -.. code:: bash +1) Using cephadm + + .. code:: bash + + $ MDS=1 MON=1 OSD=3 NFS=1 ../src/vstart.sh -n -d --cephadm + + It can deploy only single ganesha daemon with vstart on default ganesha port. + +2) Using test orchestrator + + .. code:: bash + + $ MDS=1 MON=1 OSD=3 NFS=1 ../src/vstart.sh -n -d - $ MDS=1 MON=1 OSD=3 NFS=1 ../src/vstart.sh -n -d + It can deploy multiple ganesha daemons on random port. But this requires + ganesha packages to be installed. -NFS: It denotes the number of NFS-Ganesha clusters to be created. +NFS: It is the number of NFS-Ganesha clusters to be created. Mount ===== -- 2.39.5