From: Abhishek Lekshmanan <abhishek@suse.com>
To: ceph-announce@ceph.io, ceph-users@ceph.io, dev@ceph.io,
ceph-devel@vger.kernel.org, ceph-maintainers@ceph.io
Subject: v13.2.9 Mimic released
Date: Thu, 16 Apr 2020 20:46:12 +0200 [thread overview]
Message-ID: <87zhbbl157.fsf@suse.com> (raw)
We're glad to announce the availability of the ninth and very likely the
last stable release in the Ceph Mimic stable release series. This
release fixes bugs across all components and also contains a RGW
security fix. We recommend all mimic users to upgrade to this version.
We thank everyone for making this release a possibility.
Notable Changes
---------------
* CVE-2020-1760: Fixed XSS due to RGW GetObject header-splitting
* The configuration value `osd_calc_pg_upmaps_max_stddev` used for upmap
balancing has been removed. Instead use the mgr balancer config
`upmap_max_deviation` which now is an integer number of PGs of deviation
from the target PGs per OSD. This can be set with a command like
`ceph config set mgr mgr/balancer/upmap_max_deviation 2`. The default
`upmap_max_deviation` is 1. There are situations where crush rules
would not allow a pool to ever have completely balanced PGs. For example, if
crush requires 1 replica on each of 3 racks, but there are fewer OSDs in 1 of
the racks. In those cases, the configuration value can be increased.
* The `cephfs-data-scan scan_links` command now automatically repair inotables
and snaptable.
For the full changelog please refer to the official release blog entry
at https://ceph.io/releases/v13-2-9-mimic-released
Getting Ceph
------------
* Git at git://github.com/ceph/ceph.git
* Tarball at http://download.ceph.com/tarballs/ceph-13.2.9.tar.gz
* For packages, see
http://docs.ceph.com/docs/master/install/get-packages/
* Release git sha1: 58a2a9b31fd08d8bb3089fce0e312331502ff945
--
Abhishek Lekshmanan
SUSE Software Solutions Germany GmbH
GF: Felix Imendörffer
reply other threads:[~2020-04-16 18:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhbbl157.fsf@suse.com \
--to=abhishek@suse.com \
--cc=ceph-announce@ceph.io \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-maintainers@ceph.io \
--cc=ceph-users@ceph.io \
--cc=dev@ceph.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.