Hi Folks,
Canceling the perf meeting for today. Status this week is that several
of the RGW performance PRs merged and aclamk is working on performance
testing of his large rocksdb sharding PR (which will hopefully merge
soon!). Hopefully we'll have more performance data and some intial work
toward tuning in the coming weeks.
Thanks!
Mark
Hello,
Yesterday I copied dgallowa in "Heavily-linked lists.ceph.com
pipermail archive now appears to lead to 404s" on ceph-users, but one
of the subscribers reached out to me saying that they do not see him on
the CC.
This looks like a feature of mailman that has bitten others before:
https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg02639.html
> > mailman has an (extremely annoying, in my opinion) habit of munging cc:
> > lines to drop the name of any recipient who has set their list delivery
> > options to avoid duplicate messages where the recipient is in cc.
> > Ultimately, the end user still gets the messages (reply-to-all gets the
> > message back to the list, even though it drops the cc), but at the
> > expense of not directly going to the inbox as desired. At least I still
> > only get one copy of the message, but yes, I'd rather have that one copy
> > come directly to me for all messages in the thread, rather than through
> > the list because I was munged out of cc.
> >
> > I hope that mailman3/hyperkitty will have saner defaults and not munge
> > cc lists to exclude subscribers merely based on their preference on
> > duplicate mail receipt.
>
> Wow! You are right:
>
> I checked my @redhat.com inbox and I see address@hidden has
> Kevin in CC.
>
> I checked my @gmail.com inbox (subscribed to mailing list) and I see
> address@hidden does not have Kevin in CC.
>
> I guess my @redhat.com email was received directly from Max because I
> was in CC list. It didn't pass through Mailman. I saw the original,
> unmodified list of CCs with Kevin included.
>
> The @gmail.com email was received from the mailing list. Mailman did
> what you described.
>
> This means I cannot send "Please CC maintainer" emails anymore because
> I cannot be sure whether the maintainer was CCed!
mailman3 that all ceph.io lists were transitioned to is apparently
slightly saner in that this functionality is implemented as a handler,
which can (hopefully!) be disabled by removing it from the pipeline:
https://gitlab.com/mailman/mailman/blob/master/src/mailman/handlers/avoid_d…https://gitlab.com/mailman/mailman/blob/master/src/mailman/handlers/docs/av…
I'm proposing that we disable this handler for all ceph.io lists. It
confuses everyone and it's not clear if it is actually doing any good
to anyone. gmail and other similar systems already deduplicate without
munging the headers for everyone and folks who are filtering locally
probably already have a generic rule for discarding duplicates.
IMO the mailing list software should never touch To or Cc. Thoughts?
Thanks,
Ilya
This is the third bug fix release of Ceph Nautilus release series. This
release fixes a security issue. 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
---------------
* CVE-2019-10222 - Fixed a denial of service vulnerability where an
unauthenticated client of Ceph Object Gateway could trigger a crash from an
uncaught exception
* Nautilus-based librbd clients can now open images on Jewel clusters.
* The RGW `num_rados_handles` has been removed. If you were using a value of
`num_rados_handles` greater than 1, multiply your current
`objecter_inflight_ops` and `objecter_inflight_op_bytes` parameters by the
old `num_rados_handles` to get the same throttle behavior.
* The secure mode of Messenger v2 protocol is no longer experimental with this
release. This mode is now the preferred mode of connection for monitors.
* "osd_deep_scrub_large_omap_object_key_threshold" has been lowered to detect an
object with large number of omap keys more easily.
For a detailed changelog please refer to the official release notes
entry at the ceph blog: https://ceph.io/releases/v14-2-3-nautilus-released/
Getting Ceph
------------
* Git at git://github.com/ceph/ceph.git
* Tarball at http://download.ceph.com/tarballs/ceph-14.2.3.tar.gz
* For packages, see http://docs.ceph.com/docs/master/install/get-packages/
* Release git sha1: 0f776cf838a1ae3130b2b73dc26be9c95c6ccc39
--
Abhishek Lekshmanan
SUSE Software Solutions Germany GmbH
Hi everyone,
CDM is tonight at 0100 UTC (9pm ET, 6pm PT).
https://bluejeans.com/908675367/https://tracker.ceph.com/projects/ceph/wiki/Planning
The agenda so far:
https://tracker.ceph.com/projects/ceph/wiki/CDM_04-SEP-2019
- [Yehuda] wandering log: a multi-reader, multi-writer FIFO queue striped
over rados objects. This satisfies some rgw multisite use-cases, but
should be a generic library that can be used for other things as well.
- [Sage] rados: return bufferlist with write operations. Historically
we've recorded a return code only. The idea here is to also allow a
(bounded) return buffer with arbitrary data from writes.
- [Ivo] github actions workflows for Ceph. Portable
dev/packaging/testing/benchmarking workflows based on github actions..
See you tonight!
sage