From fec8bbf5cd3e3dd72d05c4eb23209c84f056edda Mon Sep 17 00:00:00 2001 From: Varsha Rao Date: Mon, 22 Mar 2021 17:21:53 +0530 Subject: [PATCH] doc/cephfs/nfs: Add note about cephadm NFS-Ganesha daemon port Fixes: https://tracker.ceph.com/issues/49921 Signed-off-by: Varsha Rao --- doc/cephfs/fs-nfs-exports.rst | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/doc/cephfs/fs-nfs-exports.rst b/doc/cephfs/fs-nfs-exports.rst index df2d69bfc35..282a5e2842d 100644 --- 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. + ```` 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. -- 2.39.5