From: Travis Rhoden Date: Thu, 7 May 2015 20:09:29 +0000 (+0000) Subject: Update docs and changelog about rgw daemon naming X-Git-Tag: v1.5.24~9^2~1 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=099ab91cf4986ed8a0d2146cd4533c72273634b4;p=ceph-deploy.git Update docs and changelog about rgw daemon naming Signed-off-by: Travis Rhoden --- diff --git a/docs/source/changelog.rst b/docs/source/changelog.rst index 9fa009d..9de855d 100644 --- a/docs/source/changelog.rst +++ b/docs/source/changelog.rst @@ -10,6 +10,7 @@ Changelog * Use version 0.0.25 of `remoto` that fixes an issue where output would be cut (https://github.com/alfredodeza/remoto/issues/15). +* Automatically prefix custom RGW daemon names with 'rgw.' 1.5.23 ^^^^^^ diff --git a/docs/source/rgw.rst b/docs/source/rgw.rst index 102e654..4a060c5 100644 --- a/docs/source/rgw.rst +++ b/docs/source/rgw.rst @@ -17,6 +17,13 @@ corresponding service. The daemon will listen on the default port of 7480. The RGW instances will default to having a name corresponding to the hostname where it runs. For example, ``rgw.node1``. +If a custom name is desired for the RGW daemon, it can be specific like:: + + ceph-deploy rgw create node1:foo + +Custom names are automatically prefixed with "rgw.", so the resulting daemon +name would be "rgw.foo". + .. note:: If an error is presented about the ``bootstrap-rgw`` keyring not being found, that is because the ``bootstrap-rgw`` only been auto-created on new clusters starting with the Hammer release.