From: Sage Weil <sage@inktank.com>
Date: Wed, 11 Dec 2013 23:39:37 +0000 (-0800)
Subject: PendingReleaseNotes: note CRUSH and hashpspool default changes
X-Git-Tag: v0.75~121
X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=03429d1e4d2a7f5aa5cd0ba41fc4562eb28f8114;p=ceph.git

PendingReleaseNotes: note CRUSH and hashpspool default changes

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

diff --git a/PendingReleaseNotes b/PendingReleaseNotes
index 156c5147a351..409d6db66cf2 100644
--- a/PendingReleaseNotes
+++ b/PendingReleaseNotes
@@ -1,3 +1,27 @@
+v0.74
+~~~~~
+
+- We now default to the 'bobtail' CRUSH tunable values that are first supported
+  by Ceph clients in bobtail (v0.48) and Linux kernel version v3.9.  If you
+  plan to access a newly created Ceph cluster with an older kernel client, you
+  should use 'ceph osd crush tunables legacy' to switch back to the legacy
+  behavior.  Note that making that change will likely result in some data
+  movement in the system, so adjust the setting before populating the new
+  cluster with data.
+
+- We now set the HASHPSPOOL flag on newly created pools (and new
+  clusters) by default.  Support for this flag first appeared in
+  v0.64; v0.67 Dumpling is the first major release that supports it.
+  It is first supported by the Linux kernel version v3.9.  If you plan
+  to access a newly created Ceph cluster with an older kernel or
+  clients (e.g, librados, librbd) from a pre-dumpling Ceph release,
+  you should add 'osd pool default flag hashpspool = false' to the
+  '[global]' section of your 'ceph.conf' prior to creating your
+  monitors (e.g., after 'ceph-deploy new' but before 'ceph-deploy mon
+  create ...').
+
+
+
 v0.73
 ~~~~~