doc/rados update bluestore-migration to use ceph-volume

Signed-off-by: Alfredo Deza <adeza@redhat.com>
(cherry picked from commit 814b5b1658b0de4a58c1ecbfc0687a99b4513fd3)

diff --git a/doc/rados/operations/bluestore-migration.rst b/doc/rados/operations/bluestore-migration.rst
index e0d56d8a23886600949fb8f86ff40e398cb2cd2f..b6d45b030bf0c35034c00da7d0db0ee0f65215fa 100644 (file)
--- a/doc/rados/operations/bluestore-migration.rst
+++ b/doc/rados/operations/bluestore-migration.rst
@@ -69,11 +69,11 @@ more data migration than should be necessary, so it is not optimal.
 
      umount /var/lib/ceph/osd/ceph-$ID
 
-#. Destroy the OSD data.  Be *EXTREMELY CAREFUL* as this will destroy
+#. Destroy the OSD data. Be *EXTREMELY CAREFUL* as this will destroy
    the contents of the device; be certain the data on the device is
    not needed (i.e., that the cluster is healthy) before proceeding. ::
 
-     ceph-disk zap $DEVICE
+     ceph-volume lvm zap $DEVICE
 
 #. Tell the cluster the OSD has been destroyed (and a new OSD can be
    reprovisioned with the same ID)::
@@ -84,7 +84,7 @@ more data migration than should be necessary, so it is not optimal.
    This requires you do identify which device to wipe based on what you saw
    mounted above. BE CAREFUL! ::
 
-     ceph-disk prepare --bluestore $DEVICE --osd-id $ID
+     ceph-volume create --bluestore --data $DEVICE --osd-id $ID
 
 #. Repeat.
 
@@ -171,10 +171,10 @@ Migration process
 
 If you're using a new host, start at step #1.  For an existing host,
 jump to step #5 below.
-     
+
 #. Provision new BlueStore OSDs for all devices::
 
-     ceph-disk prepare --bluestore /dev/$DEVICE
+     ceph-volume lvm create --bluestore --data /dev/$DEVICE
 
 #. Verify OSDs join the cluster with::
 
@@ -231,7 +231,7 @@ jump to step #5 below.
 #. Wipe the old OSD devices. This requires you do identify which
    devices are to be wiped manually (BE CAREFUL!). For each device,::
 
-     ceph-disk zap $DEVICE
+     ceph-volume lvm zap $DEVICE
 
 #. Use the now-empty host as the new host, and repeat::
 
@@ -265,7 +265,7 @@ old device is reclaimed to convert the next OSD.
 Caveats:
 
 * This strategy requires that a blank BlueStore OSD be prepared
-  without allocating a new OSD ID, something that the ``ceph-disk``
+  without allocating a new OSD ID, something that the ``ceph-volume``
   tool doesn't support.  More importantly, the setup of *dmcrypt* is
   closely tied to the OSD identity, which means that this approach
   does not work with encrypted OSDs.