doc/cephadm: explain different methods of cephadm delivery

Explain that only in Reef and later releases is cephadm distributed as
an executable compiled from source code. This note is to go into Quincy
and only into Quincy, to direct new users of Ceph whom circumstance has
delivered into the hands of Quincy and who might have the wrong idea
that the documentation of Reef and later releases applies to their
release.

Signed-off-by: Zac Dover <zac.dover@proton.me>

diff --git a/doc/cephadm/install.rst b/doc/cephadm/install.rst
index cd1c71b0b3ec3f5d4dcf13961933b2902e8e42ec..2562647df2c7c1ce45d24f8d3fa4f493e6d12e9d 100644 (file)
--- a/doc/cephadm/install.rst
+++ b/doc/cephadm/install.rst
@@ -41,9 +41,8 @@ There are two ways to install ``cephadm``:
 #. a :ref:`curl-based installation<cephadm_install_curl>` method
 #. :ref:`distribution-specific installation methods<cephadm_install_distros>`
 
-.. note:: Recent versions of cephadm are distributed as an executable compiled
-   from source code.  Unlike for earlier versions of Ceph it is no longer
-   sufficient to copy a single script from Ceph's git tree and run it. 
+.. note:: In Quincy, cephadm is not distributed as an executable compiled from
+   source code. That feature was introduced in the Reef release.
 
 .. _cephadm_install_distros: