This is the second bug fix release of Ceph Nautilus release series. We
recommend all Nautilus users upgrade to this release. For upgrading from older
releases of ceph, general guidelines for upgrade to nautilus must be followed.
Notable Changes
---------------
* The no{up,down,in,out} related commands have been revamped. There are now 2
ways to set the no{up,down,in,out} flags: the old 'ceph osd [un]set <flag>'
command, which sets cluster-wide flags; and the new 'ceph osd [un]set-group
<flags> <who>' command, which sets flags in batch at the granularity of any
crush node, or device class.
* radosgw-admin introduces two subcommands that allow the managing of
expire-stale objects that might be left behind after a bucket reshard in
earlier versions of RGW. One subcommand lists such objects and the other
deletes them. Read the troubleshooting section of the dynamic resharding docs
for details.
* Earlier Nautilus releases (14.2.1 and 14.2.0) have an issue where deploying a
single new (Nautilus) BlueStore OSD on an upgraded cluster (i.e. one that was
originally deployed pre-Nautilus) breaks the pool utilization stats reported
by ceph df. Until all OSDs have been reprovisioned or updated (via
ceph-bluestore-tool repair), the pool stats will show values that are lower
than the true value. This is resolved in 14.2.2, such that the cluster only
switches to using the more accurate per-pool stats after all OSDs are 14.2.2
(or later), are BlueStore, and (if they were created prior to Nautilus) have
been updated via the repair function.
* The default value for mon_crush_min_required_version has been changed from
firefly to hammer, which means the cluster will issue a health warning if
your CRUSH tunables are older than hammer. There is generally a small (but
non-zero) amount of data that will move around by making the switch to hammer
tunables.
If possible, we recommend that you set the oldest allowed client to hammer or
later. You can tell what the current oldest allowed client is with:
ceph osd dump | grep min_compat_client
If the current value is older than hammer, you can tell whether it is safe to
make this change by verifying that there are no clients older than hammer
current connected to the cluster with:
ceph features
The newer straw2 CRUSH bucket type was introduced in hammer, and ensuring
that all clients are hammer or newer allows new features only supported for
straw2 buckets to be used, including the crush-compat mode for the Balancer.
For a detailed changelog please refer to the official release notes
entry at the ceph blog: https://ceph.com/releases/v14-2-2-nautilus-released/
Getting Ceph
------------
* Git at git://github.com/ceph/ceph.git
* Tarball at http://download.ceph.com/tarballs/ceph-14.2.2.tar.gz
* For packages, see http://docs.ceph.com/docs/master/install/get-packages/
* Release git sha1: 4f8fa0a0024755aae7d95567c63f11d6862d55be
Hi all
A couple of days ago marks a new day in the 26-year history of Red
Hat. IBM has finalized its acquisition of Red Hat, which will operate
as a distinct unit within IBM moving forward.
What does this mean for Red Hat’s contributions to the Ceph project?
In short, nothing.
Red Hat always has and will continue to be a champion for open source
and projects like Ceph. IBM is committed to Red Hat’s independence and
role in open source software communities so that we can continue this
work without interruption or changes.
Our mission, governance, and objectives remain the same. We will
continue to execute the existing project roadmap. Red Hat associates
will continue to contribute to the upstream in the same ways they have
been. And, as always, we will continue to help upstream projects be
successful and contribute to welcoming new members and maintaining the
project.
We will do this together, with the community, as we always have.
If you have questions or would like to learn more about today’s news,
I encourage you to review the list of materials below. Red Hat CTO
Chris Wright will host an online Q&A session in the coming days where
you can ask questions you may have about what the acquisition means
for Red Hat and our involvement in open source communities. Details
will be announced on the Red Hat blog.
- Press release:
https://www.redhat.com/en/about/press-releases/ibm-closes-landmark-acquisit…
- Chris Wright blog - Red Hat and IBM: Accelerating the adoption of
open source: https://www.redhat.com/en/blog/red-hat-and-ibm-accelerating-adoption-open-s…
- FAQ on Red Hat Community Blog:
https://community.redhat.com/blog/2019/07/faq-for-communities/
--
Mike Perez (thingee)
Ceph Community Manager - Red Hat Open Source Program Office
Hi everyone,
The target release date for Octopus is March 1, 2020.
The freeze will be January 1, 2020. As a practical matter, that means any
features need to be in before people leave for the holidays, ensuring the
features get in in time and also that we can run tests over the holidays
while the test lab is relatively idle.
We plan to stick to a 12 month cadence going forward, so the P release
target would be March 1 2021 (regardless of whether Octopus is early or
late).
Thanks!
sage
