doc/release-notes: note about ceph-deploy

Signed-off-by: Sage Weil <sage@inktank.com>

diff --git a/doc/release-notes.rst b/doc/release-notes.rst
index c17bb4c888913850694e9d37cd3bfbb9b5271997..1022a0743746a23d42a03b3b596c38bfd8061850 100644 (file)
--- a/doc/release-notes.rst
+++ b/doc/release-notes.rst
@@ -8,6 +8,13 @@ v0.61 "Cuttlefish"
 Upgrading from v0.60
 ~~~~~~~~~~~~~~~~~~~~
 
+* The ceph-deploy tool is now the preferred method of provisioning
+  new clusters.  For existing clusters created via mkcephfs that
+  would like to transition to the new tool, there is a migration
+  path, documented at `Transitioning to ceph-deploy`_.
+
+.. _Transitioning to ceph-deploy: rados/deployment/ceph-deploy-transition
+
 * radosgw-admin now uses the term zone instead of cluster to describe
   each instance of the radosgw data store (and corresponding
   collection of radosgw daemons).  The usage for the radosgw-admin
@@ -40,6 +47,13 @@ Please see `Upgrading from Bobtail to Cuttlefish`_ for details.
 
 .. _Upgrading from Bobtail to Cuttlefish: ../install/upgrading-ceph/#upgrading-from-bobtail-to-cuttlefish
 
+* The ceph-deploy tool is now the preferred method of provisioning
+  new clusters.  For existing clusters created via mkcephfs that
+  would like to transition to the new tool, there is a migration
+  path, documented at `Transitioning to ceph-deploy`_.
+
+.. _Transitioning to ceph-deploy: rados/deployment/ceph-deploy-transition
+
 * radosgw-admin now uses the term zone instead of cluster to describe
   each instance of the radosgw data store (and corresponding
   collection of radosgw daemons).  The usage for the radosgw-admin