doc/cephfs/nfs: Add note about cephadm NFS-Ganesha daemon port

Fixes: https://tracker.ceph.com/issues/49921
Signed-off-by: Varsha Rao <varao@redhat.com>
(cherry picked from commit fec8bbf5cd3e3dd72d05c4eb23209c84f056edda)

diff --git a/doc/cephfs/fs-nfs-exports.rst b/doc/cephfs/fs-nfs-exports.rst
index cf5a73e7efa60a6dfe80e3ee104e266918b9ec75..3708bb251461c0b3628855a8a6747525e7ef00f7 100644 (file)
--- a/doc/cephfs/fs-nfs-exports.rst
+++ b/doc/cephfs/fs-nfs-exports.rst
@@ -25,6 +25,9 @@ This creates a common recovery pool for all NFS Ganesha daemons, new user based
    orchestrator module (see :doc:`/mgr/orchestrator`) such as "mgr/cephadm", at
    least one such module must be enabled for it to work.
 
+   Currently, NFS Ganesha daemon deployed by cephadm listens on the standard
+   port. So only one daemon will be deployed on a host.
+
 ``<type>`` signifies the export type, which corresponds to the NFS Ganesha file
 system abstraction layer (FSAL). Permissible values are ``"cephfs`` or
 ``rgw``, but currently only ``cephfs`` is supported.
@@ -40,11 +43,11 @@ daemon running per node). For example, the following placement string means
 
     "host1,host2"
 
-and this placement specification says to deploy two NFS Ganesha daemons each
-on nodes host1 and host2 (for a total of four NFS Ganesha daemons in the
+and this placement specification says to deploy single NFS Ganesha daemon each
+on nodes host1 and host2 (for a total of two NFS Ganesha daemons in the
 cluster)::
 
-    "4 host1,host2"
+    "2 host1,host2"
 
 For more details, refer :ref:`orchestrator-cli-placement-spec` but keep
 in mind that specifying the placement via a YAML file is not supported.