From: Nathan Cutler Date: Thu, 16 Jul 2020 12:19:29 +0000 (+0200) Subject: doc: cephfs: fix misleading "ceph fs volume create" command X-Git-Tag: v15.2.8~5^2~1^2~39^2~5 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=c22cbdef8cf6b463ca450ce9dc1a09007a647a1b;p=ceph.git doc: cephfs: fix misleading "ceph fs volume create" command The "ceph fs volume create" command takes a placement string, just like "ceph nfs cluster create" does. Align the documentation so the placement string is explained in the same manner in both places. Signed-off-by: Nathan Cutler (cherry picked from commit 6f0c2496d6a40505164161acbb835b306ee8914f) --- diff --git a/doc/cephfs/fs-volumes.rst b/doc/cephfs/fs-volumes.rst index 4efe26d8b642..3048cf954f97 100644 --- a/doc/cephfs/fs-volumes.rst +++ b/doc/cephfs/fs-volumes.rst @@ -45,9 +45,29 @@ Create a volume using:: $ ceph fs volume create [] -This creates a CephFS file system and its data and metadata pools. It also tries -to create MDSes for the filesystem using the enabled ceph-mgr orchestrator -module (see :doc:`/mgr/orchestrator`) , e.g., rook. +This creates a CephFS file system and its data and metadata pools. It can also +try to create MDSes for the filesystem using the enabled ceph-mgr orchestrator +module (see :doc:`/mgr/orchestrator`), e.g. rook. + + is the volume name (an arbitrary string), and + + is an optional string signifying which hosts should have NFS Ganesha +daemon containers running on them and, optionally, the total number of NFS +Ganesha daemons the cluster (should you want to have more than one NFS Ganesha +daemon running per node). For example, the following placement string means +"deploy NFS Ganesha daemons on nodes host1 and host2 (one daemon per host): + + "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 +cluster): + + "4 host1,host2" + +For more details on placement specification refer to the `orchestrator doc +`_ +but keep in mind that specifying the placement via a YAML file is not supported. Remove a volume using::