From 41987db876a572f9feed7300a2c39789454611fa Mon Sep 17 00:00:00 2001 From: Sage Weil Date: Wed, 1 Jan 2014 17:58:30 -0800 Subject: [PATCH] doc/release-notes: v0.74 Signed-off-by: Sage Weil --- PendingReleaseNotes | 34 -------------------- doc/release-notes.rst | 74 +++++++++++++++++++++++++++++++++++++++++-- 2 files changed, 72 insertions(+), 36 deletions(-) diff --git a/PendingReleaseNotes b/PendingReleaseNotes index 65b4f1ab7400b..f813e86622c04 100644 --- a/PendingReleaseNotes +++ b/PendingReleaseNotes @@ -6,37 +6,3 @@ v0.75 non-plain format. This is consistent with the behavior for a pool which used to hold images, but contains none. Scripts relying on this behavior should be updated. - -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 ...'). - -- The configuration option 'osd pool default crush rule' is deprecated - and replaced with 'osd pool default crush replicated ruleset'. 'osd - pool default crush rule' takes precedence for backward compatibility - and a deprecation warning is displayed when it is used. - -v0.72.2 -~~~~~~~ -- As part of fix for #6796, 'ceph osd pool set ' now - receives as an integer instead of a string. This affects how - 'hashpspool' flag is set/unset: instead of 'true' or 'false', it now - must be '0' or '1'. diff --git a/doc/release-notes.rst b/doc/release-notes.rst index c3f7960d9987b..8113fca69911c 100644 --- a/doc/release-notes.rst +++ b/doc/release-notes.rst @@ -2,6 +2,70 @@ Release Notes =============== +v0.74 +----- + +This release includes a few substantial pieces for Firefly, including +a long-overdue switch to 3x replication by default and a switch to the +"new" CRUSH tunables by default (supported since bobtail). There is +also a fix for a long-standing radosgw bug (stalled GET) that has +already been backported to emperor and dumpling. + +Upgrading +~~~~~~~~~ + +* 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 ...'). + +* The configuration option 'osd pool default crush rule' is deprecated + and replaced with 'osd pool default crush replicated ruleset'. 'osd + pool default crush rule' takes precedence for backward compatibility + and a deprecation warning is displayed when it is used. + +Notable Changes +~~~~~~~~~~~~~~~ + +* buffer: some zero-copy groundwork (Josh Durgin) +* ceph-disk: avoid fd0 (Loic Dachary) +* crush: default to bobtail tunables (Sage Weil) +* crush: many additional tests (Loic Dachary) +* crush: misc fixes, cleanups (Loic Dachary) +* crush: new rule steps to adjust retry attempts (Sage Weil) +* debian: integrate misc fixes from downstream packaging (James Page) +* doc: big update to install docs (John Wilkins) +* libcephfs: fix resource leak (Zheng Yan) +* misc coverity fixes (Xing Lin, Li Wang, Danny Al-Gaaf) +* misc portability fixes (Noah Watkins, Alan Somers) +* mon, osd: new 'erasure' pool type (still not fully supported) +* mon: add 'mon getmap EPOCH' (Joao Eduardo Luis) +* mon: collect misc metadata about osd (os, kernel, etc.), new 'osd metadata' command (Sage Weil) +* osd: default to 3x replication +* osd: do not include backfill targets in acting set (David Zafman) +* osd: new 'chassis' type in default crush hierarchy (Sage Weil) +* osd: requery unfound on stray notify (#6909) (Samuel Just) +* osd: some PGBackend infrastructure (Samuel Just) +* osd: support for new 'memstore' (memory-backed) backend (Sage Weil) +* rgw: fix fastcgi deadlock (do not return data from librados callback) (Yehuda Sadeh) +* rgw: fix reading bucket policy (#6940) +* rgw: fix use-after-free when releasing completion handle (Yehuda Sadeh) + + v0.73 ----- @@ -31,8 +95,8 @@ Upgrading object. -Notable Changes: -~~~~~~~~~~~~~~~~ +Notable Changes +~~~~~~~~~~~~~~~ * ceph-crush-location: new hook for setting CRUSH location of osd daemons on start * ceph-kvstore-tool: expanded command set and capabilities (Joao Eduardo Luis) @@ -72,6 +136,12 @@ Upgrading avoid issuing this particular command via the CLI while there is a mix of v0.72.1 and v0.72.2 monitor daemons running. +* As part of fix for #6796, 'ceph osd pool set ' now + receives as an integer instead of a string. This affects how + 'hashpspool' flag is set/unset: instead of 'true' or 'false', it now + must be '0' or '1'. + + Changes ~~~~~~~ -- 2.39.5