doc: deprecate the cache tiering

This topic has been discussed many times; recently at the Dev
Summit of Cephalocon 2023.

This commit is the minial version of the work, contained entirely
within the `doc`. However, likely it will be expanded as there
were ideas like e.g. adding cache tiering back experimental feature
list (Sam) to warn users when deploying a new cluster.

Signed-off-by: Radosław Zarzyński <rzarzyns@redhat.com>

diff --git a/PendingReleaseNotes b/PendingReleaseNotes
index 91015cf7dd3f0594b41ee547543bd6e0de2b219d..a5a20b9dbe62fd311dcfffc4ebeefe377ba3e66a 100644 (file)
--- a/PendingReleaseNotes
+++ b/PendingReleaseNotes
@@ -138,6 +138,7 @@
   `ceph config set mgr mgr/telemetry/leaderboard_description ‘Cluster description’`.
 * CEPHFS: After recovering a Ceph File System post following the disaster recovery
   procedure, the recovered files under `lost+found` directory can now be deleted.
+* core: cache-tiering is now deprecated.
 
 >=17.2.1
 

diff --git a/doc/rados/operations/cache-tiering.rst b/doc/rados/operations/cache-tiering.rst
index 8056ace4743bd628a8b6296c693bb08bd3230a2e..cd29b87d0cfa67c2c20f6d65bea31c2e6b9e1934 100644 (file)
--- a/doc/rados/operations/cache-tiering.rst
+++ b/doc/rados/operations/cache-tiering.rst
@@ -1,6 +1,10 @@
 ===============
  Cache Tiering
 ===============
+.. warning:: Cache tiering has been deprecated in the Reef release as it
+             has lacked a maintainer for a very long time. This does not mean
+             it will be certainly removed, but we may choose to remove it
+             without much further notice.
 
 A cache tier provides Ceph Clients with better I/O performance for a subset of
 the data stored in a backing storage tier. Cache tiering involves creating a