From: Guillaume Abrioux Date: Fri, 9 Apr 2021 12:28:46 +0000 (+0200) Subject: doc/rgw-nfs: use same pattern for keyring name X-Git-Tag: v17.1.0~827^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=5d97fd2d8e414b3ade155c11e0292ee3772f22a0;p=ceph.git doc/rgw-nfs: use same pattern for keyring name Just for keeping consistency everywhere this documentation mentions a keyring name. Signed-off-by: Guillaume Abrioux --- diff --git a/doc/radosgw/nfs.rst b/doc/radosgw/nfs.rst index 336736e4cc5..84d62bcec09 100644 --- a/doc/radosgw/nfs.rst +++ b/doc/radosgw/nfs.rst @@ -117,7 +117,7 @@ ceph.conf Required ceph.conf configuration for RGW NFS includes: -* valid [client.radosgw.{instance-name}] section +* valid [client.rgw.{instance-name}] section * valid values for minimal instance configuration, in particular, an installed and correct ``keyring`` Other config variables are optional, front-end-specific and front-end @@ -304,7 +304,7 @@ Ceph configuration file to change the refresh rate. If exporting Swift containers that do not conform to valid S3 bucket naming requirements, set ``rgw_relaxed_s3_bucket_names`` to true in the -[client.radosgw] section of the Ceph configuration file. For example, +[client.rgw] section of the Ceph configuration file. For example, if a Swift container name contains underscores, it is not a valid S3 bucket name and will be rejected unless ``rgw_relaxed_s3_bucket_names`` is set to true.