docs: warning and remove few docs section for Filestore

Update docs after filestore removal.

Signed-off-by: Nitzan Mordechai <nmordech@redhat.com>

6 files changed, 5 insertions, 20 deletions

diff --git a/doc/rados/configuration/common.rst b/doc/rados/configuration/common.rst
index 1d218a6f11a..06b3e9160bc 100644
--- a/doc/rados/configuration/common.rst
+++ b/doc/rados/configuration/common.rst
@@ -103,20 +103,6 @@ Reference`_.
 OSDs
 ====
 
-When Ceph production clusters deploy :term:`Ceph OSD Daemons`, the typical
-arrangement is that one node has one OSD daemon running Filestore on one
-storage device. BlueStore is now the default back end, but when using Filestore
-you must specify a journal size. For example:
-
-.. code-block:: ini
-
-    [osd]
-    osd_journal_size = 10000
-
-    [osd.0]
-    host = {hostname} #manual deployments only.
-
-
 By default, Ceph expects to store a Ceph OSD Daemon's data on the following
 path::
 
diff --git a/doc/rados/configuration/filestore-config-ref.rst b/doc/rados/configuration/filestore-config-ref.rst
index 8c7e9ab8444..c9a3cb285f4 100644
--- a/doc/rados/configuration/filestore-config-ref.rst
+++ b/doc/rados/configuration/filestore-config-ref.rst
@@ -1,6 +1,7 @@
 ============================
  Filestore Config Reference
 ============================
+.. warning:: Filestore has been deprecated in the Reef release and is no longer supported.
 
 The Filestore back end is no longer the default when creating new OSDs,
 though Filestore OSDs are still supported.
diff --git a/doc/rados/configuration/journal-ref.rst b/doc/rados/configuration/journal-ref.rst
index ccf7e09f158..5ce5a5e2dd1 100644
--- a/doc/rados/configuration/journal-ref.rst
+++ b/doc/rados/configuration/journal-ref.rst
@@ -1,7 +1,7 @@
 ==========================
  Journal Config Reference
 ==========================
-
+.. warning:: Filestore has been deprecated in the Reef release and is no longer supported.
 .. index:: journal; journal configuration
 
 Filestore OSDs use a journal for two reasons: speed and consistency.  Note
diff --git a/doc/rados/configuration/mclock-config-ref.rst b/doc/rados/configuration/mclock-config-ref.rst
index f2a1603b5dc..dccf6ef251c 100644
--- a/doc/rados/configuration/mclock-config-ref.rst
+++ b/doc/rados/configuration/mclock-config-ref.rst
@@ -7,10 +7,6 @@
 QoS support in Ceph is implemented using a queuing scheduler based on `the
 dmClock algorithm`_. See :ref:`dmclock-qos` section for more details.
 
-.. note:: The *mclock_scheduler* is supported for BlueStore OSDs. For Filestore
-          OSDs the *osd_op_queue* is set to *wpq* and is enforced even if you
-          attempt to change it.
-
 To make the usage of mclock more user-friendly and intuitive, mclock config
 profiles are introduced. The mclock profiles mask the low level details from
 users, making it easier to configure and use mclock.
diff --git a/doc/rados/configuration/osd-config-ref.rst b/doc/rados/configuration/osd-config-ref.rst
index deffd6103f3..3c3b378e7b4 100644
--- a/doc/rados/configuration/osd-config-ref.rst
+++ b/doc/rados/configuration/osd-config-ref.rst
@@ -7,7 +7,7 @@
 You can configure Ceph OSD Daemons in the Ceph configuration file (or in recent
 releases, the central config store), but Ceph OSD
 Daemons can use the default values and a very minimal configuration. A minimal
-Ceph OSD Daemon configuration sets ``osd journal size`` (for Filestore), ``host``,  and
+Ceph OSD Daemon configuration sets ``host`` and
 uses default values for nearly everything else.
 
 Ceph OSD Daemons are numerically identified in incremental fashion, beginning
diff --git a/doc/rados/configuration/storage-devices.rst b/doc/rados/configuration/storage-devices.rst
index 660a2906a75..3b9d45a3d58 100644
--- a/doc/rados/configuration/storage-devices.rst
+++ b/doc/rados/configuration/storage-devices.rst
@@ -71,6 +71,8 @@ For more information, see :doc:`bluestore-config-ref` and :doc:`/rados/operation
 
 FileStore
 ---------
+.. warning:: Filestore has been deprecated in the Reef release and is no longer supported.
+
 
 FileStore is the legacy approach to storing objects in Ceph. It
 relies on a standard file system (normally XFS) in combination with a