Hello,
There's so many ways to build ceph, from sources i'm pretty confused, so i
need some help.
I want to build regularly ceph from "main/master", to create debian packets
out of it.
I somehow have a solution which is working, but what's the best practice
for doing this right now?
On top of that, I didn't find ANY solution to build a "crimson-osd" packet
out of the latest sources, i even spent hours on this, what's the correct
way to do this?
Thanks!
Sascha
hey Shilpa and team,
early in the reef cycle, https://github.com/ceph/ceph/pull/46188 was
contributed to support the combination of server-side compression and
encryption on the same object data. only recently did we catch a
regression in multisite, where such objects fail to replicate and can
cause crashes. this bug, tracked in
https://tracker.ceph.com/issues/57905, was just fixed and backported
for reef in https://github.com/ceph/ceph/pull/52297. this was a
regression in reef, so i was planning to treat it as a blocker
in that backport, i added a warning to the original release note:
RGW: Compression is now supported for objects uploaded with
Server-Side Encryption. When both are enabled, compression is applied
before encryption.
WARNING: In a multisite configuration, objects that are both
compressed and encrypted will not replicate correctly to Pacific or
Quincy. Upgrade all zones to Reef before enabling compression.
it occurs to me that we might add a new 'compress-encrypted' feature
flag to the zonegroup (similar to the 'resharding' flag in reef) to
prevent this combination of compression+encryption until all zones
upgrade and enable it. do you think that's worth doing, or is a
release note sufficient?
Hello!
Releasing Reef
---------------------
* RC2 is out but we still have several PRs to go, including blockers.
* RC3 might be worth doing but we Reef shall go before end of the month.
Misc
-------
* For the sake of unittesting of dencoders interoperatbility we're going
to impose some extra work (like registering types within ceph-dencoder)
on developers writing encodable structs. This will be discussed further
in a CDM.
* A lab issue got fixed.
Regards
Radek
Hi everyone, CDM is happening today @ 1:00 UTC. See more meeting details
below.
Please add any topics you'd like to discuss to the agenda:
https://tracker.ceph.com/projects/ceph/wiki/CDM_05-JUL-2023
Thanks, Laura Flores
Meeting link:
https://meet.jit.si/ceph-dev-monthly
Time conversions:
UTC: Thursday, July 6, 1:00 UTC
Mountain View, CA, US: Wednesday, July 5, 18:00 PDT
Phoenix, AZ, US: Wednesday, July 5, 18:00 MST
Denver, CO, US: Wednesday, July 5, 19:00 MDT
Huntsville, AL, US: Wednesday, July 5, 20:00 CDT
Raleigh, NC, US: Wednesday, July 5, 21:00 EDT
London, England: Thursday, July 6, 2:00 BST
Paris, France: Thursday, July 6, 3:00 CEST
Helsinki, Finland: Thursday, July 6, 4:00 EEST
Tel Aviv, Israel: Thursday, July 6, 4:00 IDT
Pune, India: Thursday, July 6, 6:30 IST
Brisbane, Australia: Thursday, July 6, 11:00 AEST
Singapore, Asia: Thursday, July 6, 9:00 +08
Auckland, New Zealand: Thursday, July 6, 13:00 NZST
--
Laura Flores
She/Her/Hers
Software Engineer, Ceph Storage <https://ceph.io>
Chicago, IL
lflores(a)ibm.com | lflores(a)redhat.com <lflores(a)redhat.com>
M: +17087388804
Hi,
I am planning to support read localise feature for RGW servers similar to
what RBD volumes support. From code reading, it looks to pass
"librados::OPERATION_LOCALIZE_READS" before sending the request to RADOS.
I have created a tracker issue for this feature
https://tracker.ceph.com/issues/61701, this will be per server config
option. I don't know about any other technical hurdles in implementing this
feature. Please share your thoughts on the same.
Thanks and regards,
Jiffin
