From: Lenz Grimmer Date: Thu, 31 Jan 2019 13:39:11 +0000 (+0000) Subject: doc/mgr/dashboard: NFS management instruction review X-Git-Tag: v14.1.0~199^2~4 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=3b3bea991b17cd9cfc9b8103336dc04e594ba802;p=ceph.git doc/mgr/dashboard: NFS management instruction review Signed-off-by: Lenz Grimmer --- diff --git a/doc/mgr/dashboard.rst b/doc/mgr/dashboard.rst index 5a8f14d7dccf..2cf0b14c3f92 100644 --- a/doc/mgr/dashboard.rst +++ b/doc/mgr/dashboard.rst @@ -81,7 +81,7 @@ various aspects of your Ceph cluster: counters. Display and manage (add/edit/delete) object gateway users and their details (e.g. quotas) as well as the users' buckets and their details (e.g. owner, quotas). -* **NFS-Ganesha**: Manage NFS-Ganesha exports that are stored as RADOS objects. +* **NFS**: Manage NFS exports of CephFS filesystems and RGW S3 buckets via NFS Ganesha.``` Enabling -------- @@ -620,16 +620,16 @@ A log entry may look like this:: NFS-Ganesha Management ---------------------- -Ceph Dashboard can help with the management of NFS-Ganesha exports that use +Ceph Dashboard can manage `NFS Ganesha `_ exports that use CephFS or RadosGW as their backstore. To enable this feature in Ceph Dashboard there are some assumptions that need to be met regarding the way NFS-Ganesha services are configured. -Ceph Dashboard reads NFS-Ganesha configuration from the Ceph cluster, therefore +The dashboard manages NFS-Ganesha config files stored in RADOS objects on the Ceph Cluster. NFS-Ganesha must store part of their configuration in the Ceph cluster. -The NFS-Ganesha configuration stored in the Ceph cluster must follow some +These configuration files must follow some conventions. conventions. Each export block must be stored in its own RADOS object named ``export-``, where ```` must match the ``Export_ID`` attribute of the @@ -650,9 +650,9 @@ Configuring NFS-Ganesha in the dashboard ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ To enable the management of NFS-Ganesha exports in Ceph Dashboard, we only -need to tell the Dashboard, in which RADOS pool and namespace are stored the -configuration objects. Then, Ceph Dashboard knows how search for the objects -following the naming convention described above. +need to tell the Dashboard, in which RADOS pool and namespace the +configuration objects are stored. Then, Ceph Dashboard can access the objects +by following the naming convention described above. The Dashboard command to configure the NFS-Ganesha configuration objects location is:: @@ -666,13 +666,13 @@ configuration objects and we can start manage the exports through the Web UI. Support for multiple NFS-Ganesha clusters ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -Ceph Dashboard also supports the management of NFS-Ganesha export belonging +Ceph Dashboard also supports the management of NFS-Ganesha exports belonging to different NFS-Ganesha clusters. An NFS-Ganesha cluster is a group of NFS-Ganesha service daemons sharing the same exports. Different NFS-Ganesha clusters are independent and don't share the exports configuration between each other. -Each NFS-Ganesha cluster should store their configuration objects in a +Each NFS-Ganesha cluster should store its configuration objects in a different RADOS pool/namespace to isolate the configuration from each other. To specify the locations of the configuration of each NFS-Ganesha cluster we @@ -683,6 +683,6 @@ can use the same command as above but with a different value pattern:: The ```` is an arbitrary string that should uniquely identify the NFS-Ganesha cluster. -When configuring the Ceph Dashboard with multiple NFS-Ganesha clusters the +When configuring the Ceph Dashboard with multiple NFS-Ganesha clusters, the Web UI will automatically allow to choose to which cluster an export belongs.