=====================
Cephadm deploys NFS Ganesha using a pre-defined RADOS *pool*
-and optional *namespace*
+and optional *namespace*.
To deploy a NFS Ganesha gateway, run the following command:
ceph orch apply nfs *<svc_id>* *<pool>* *<namespace>* --placement="*<num-daemons>* [*<host1>* ...]"
-For example, to deploy NFS with a service id of *foo*, that will use the RADOS
-pool *nfs-ganesha* and namespace *nfs-ns*:
+For example, to deploy NFS with a service id of *foo* that will use the RADOS
+pool *nfs-ganesha* and the namespace *nfs-ns*, run this command:
.. prompt:: bash #
ceph orch apply nfs foo nfs-ganesha nfs-ns
.. note::
- Create the *nfs-ganesha* pool first if it doesn't exist.
+ If the *nfs-ganesha* doesn't exist, create it.
-See :ref:`orchestrator-cli-placement-spec` for details of the placement specification.
+See :ref:`orchestrator-cli-placement-spec` for the details of the placement
+specification.
Service Specification
=====================
-Alternatively, an NFS service can also be applied using a YAML specification.
+Alternatively, an NFS service can be applied using a YAML specification.
-A service of type ``nfs`` requires a pool name and may contain
+A service of type ``nfs`` requires a pool name and can contain
an optional namespace:
.. code-block:: yaml
pool: mypool
namespace: mynamespace
-where ``pool`` is a RADOS pool where NFS client recovery data is stored
-and ``namespace`` is a RADOS namespace where NFS client recovery
-data is stored in the pool.
+In this example, ``pool`` is a RADOS pool where NFS client recovery data is
+stored and ``namespace`` is a RADOS namespace where NFS client recovery data
+is stored.
-The specification can then be applied using:
+The specification can then be applied by running the following command:
.. prompt:: bash #