doc/ceph-volume/activate: Users should call cephadm instead

Fixes: https://tracker.ceph.com/issues/52575
Signed-off-by: Sebastian Wagner <sewagner@redhat.com>

diff --git a/doc/ceph-volume/lvm/activate.rst b/doc/ceph-volume/lvm/activate.rst
index 5e43d4cb5f566ea711bda78bfeec951922a851c9..eef5a0101fdbfd832bd41a574152e4a9612a37db 100644 (file)
--- a/doc/ceph-volume/lvm/activate.rst
+++ b/doc/ceph-volume/lvm/activate.rst
@@ -2,6 +2,7 @@
 
 ``activate``
 ============
+          
 Once :ref:`ceph-volume-lvm-prepare` is completed, and all the various steps
 that entails are done, the volume is ready to get "activated".
 
@@ -12,6 +13,9 @@ understand what OSD is enabled and needs to be mounted.
 .. note:: The execution of this call is fully idempotent, and there is no
           side-effects when running multiple times
 
+For OSDs deployed by cephadm, please refer to :ref:cephadm-osd-activate: 
+instead.
+
 New OSDs
 --------
 To activate newly prepared OSDs both the :term:`OSD id` and :term:`OSD uuid`
@@ -24,6 +28,10 @@ need to be supplied. For example::
 
 Activating all OSDs
 -------------------
+
+.. note:: For OSDs deployed by cephadm, please refer to :ref:cephadm-osd-activate: 
+          instead.
+
 It is possible to activate all existing OSDs at once by using the ``--all``
 flag. For example::
 

diff --git a/doc/cephadm/osd.rst b/doc/cephadm/osd.rst
index f0bf47cfe547cf144a957f7799bc1de358dd7283..331ae13f7c9f67dda8b742b363ab75af723f32b8 100644 (file)
--- a/doc/cephadm/osd.rst
+++ b/doc/cephadm/osd.rst
@@ -868,6 +868,8 @@ It is also possible to specify directly device paths in specific hosts like the
 
 This can easily be done with other filters, like `size` or `vendor` as well.
 
+.. _cephadm-osd-activate:
+
 Activate existing OSDs
 ======================