RepoMirrors/ceph
1
0
Fork 0
mirror of https://github.com/ceph/ceph synced 2024-12-24 12:24:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

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

Browse Source 
Fixes: https://tracker.ceph.com/issues/49921
Signed-off-by: Varsha Rao <varao@redhat.com>
This commit is contained in:
Varsha Rao 2021-03-22 17:21:53 +05:30
parent e4cff916f2
commit fec8bbf5cd
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/cephfs/fs-nfs-exports.rst
View File

@ -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.