From: Sage Weil <sage@newdream.net>
Date: Mon, 8 Mar 2021 14:47:57 +0000 (-0500)
Subject: PendingReleaseNodes: note changes in cephadm rgw behavior
X-Git-Tag: v16.2.0~106^2~62
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=5ac5d4cc8ec129e3bd5bccc871e63a94a76dea07;p=ceph.git

PendingReleaseNodes: note changes in cephadm rgw behavior

Signed-off-by: Sage Weil <sage@newdream.net>
(cherry picked from commit f4ff70941fa585e14cdc628f913b001c208a3327)
---

diff --git a/PendingReleaseNotes b/PendingReleaseNotes
index 0438d59e9ac3..8940f9c81bff 100644
--- a/PendingReleaseNotes
+++ b/PendingReleaseNotes
@@ -254,3 +254,12 @@
 * ``ceph pg #.# list_unfound`` output has been enhanced to provide
   might_have_unfound information which indicates which OSDs may
   contain the unfound objects.
+
+* The ``ceph orch apply rgw`` syntax and behavior have changed.  RGW
+  services can now be arbitrarily named (it is no longer forced to be
+  `realm.zone`).  The ``--rgw-realm=...`` and ``--rgw-zone=...``
+  arguments are now optional, which means that if they are omitted, a
+  vanilla single-cluster RGW will be deployed.  When the realm and
+  zone are provided, the user is now responsible for setting up the
+  multisite configuration beforehand--cephadm no longer attempts to
+  create missing realms or zones.