From: Alfredo Deza Date: Fri, 20 Oct 2017 16:02:10 +0000 (-0400) Subject: doc/ceph-volume update activation to include bluestore support X-Git-Tag: v12.2.2~83^2~21 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=d65af56eaaab728d8c81ddb69b967cb13f177766;p=ceph.git doc/ceph-volume update activation to include bluestore support Signed-off-by: Alfredo Deza (cherry picked from commit 288a3124793d11d71b540555fd03c2f61a79dd16) --- diff --git a/doc/ceph-volume/lvm/activate.rst b/doc/ceph-volume/lvm/activate.rst index b9f30d69f3da..012b86baf3b9 100644 --- a/doc/ceph-volume/lvm/activate.rst +++ b/doc/ceph-volume/lvm/activate.rst @@ -17,7 +17,7 @@ New OSDs To activate newly prepared OSDs both the :term:`OSD id` and :term:`OSD uuid` need to be supplied. For example:: - ceph-volume activate --filestore 0 0263644D-0BF1-4D6D-BC34-28BD98AE3BC8 + ceph-volume activate --bluestore 0 0263644D-0BF1-4D6D-BC34-28BD98AE3BC8 .. note:: The UUID is stored in the ``osd_fsid`` file in the OSD path, which is generated when :ref:`ceph-volume-lvm-prepare` is used. @@ -58,6 +58,9 @@ The systemd unit will look for the matching OSD device, and by looking at its # start the ``ceph-osd@0`` systemd unit +.. note:: The system infers the objectstore type (filestore or bluestore) by + inspecting the LVM tags applied to the OSD devices + Existing OSDs ------------- For exsiting OSDs that have been deployed with different tooling, the only way