doc/release-notes: warn about sysvinit crush map update

See c189d855e67baadf977d8ca14509dcacd579af7a.

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

diff --git a/doc/release-notes.rst b/doc/release-notes.rst
index 68fed0101d82069e994496e3395f6979af7c3dd8..3ce7750300ee7353e67a8d65636935f5adb5e57d 100644 (file)
--- a/doc/release-notes.rst
+++ b/doc/release-notes.rst
@@ -15,6 +15,15 @@ Upgrading from v0.60
 
 .. _Transitioning to ceph-deploy: rados/deployment/ceph-deploy-transition
 
+* The sysvinit script (/etc/init.d/ceph) will now verify (and, if
+  necessary, update) the OSD's position in the CRUSH map on startup.
+  (The upstart script has always worked this way.) By default, this
+  ensures that the OSD is under a 'host' with a name that matches the
+  hostname (``hostname -s``).  Legacy clusters create with mkcephfs do
+  this by default, so this should not cause any problems, but legacy
+  clusters with customized CRUSH maps with an alternate structure
+  should set ``osd crush update on start = false``.
+
 * 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
@@ -54,6 +63,15 @@ Please see `Upgrading from Bobtail to Cuttlefish`_ for details.
 
 .. _Transitioning to ceph-deploy: rados/deployment/ceph-deploy-transition
 
+* The sysvinit script (/etc/init.d/ceph) will now verify (and, if
+  necessary, update) the OSD's position in the CRUSH map on startup.
+  (The upstart script has always worked this way.) By default, this
+  ensures that the OSD is under a 'host' with a name that matches the
+  hostname (``hostname -s``).  Legacy clusters create with mkcephfs do
+  this by default, so this should not cause any problems, but legacy
+  clusters with customized CRUSH maps with an alternate structure
+  should set ``osd crush update on start = false``.
+
 * 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