Hi all,
Based on a recent discussion in Slack [1], I'd like to raise some awareness
around the "make check arm64" CI test on our pull requests and the new
effort to maintain it.
In the original Slack thread, there was talk of disabling the test due to
lack of maintainers. However, Rongqi Sun and Rixin Luo (CC'd) have both
expressed interest in maintaining the test since Ceph in arm is playing an
important role in the China storage market, and both are regular Ceph and
arm contributors.
I raised a tracker ticket [2] to track updates on this effort.
This was also discussed in the CLT call, where leads mentioned that we
would like to bring the arm audience into more upstream discussions if
possible. Doing so would help the project improve arm test coverage in the
Ceph project as a whole.
Thanks again to Rongqi and Rixin for offering their expertise.
- Laura Flores
1. Slack thread:
https://ceph-storage.slack.com/archives/C1HFJ4VTN/p1702913385839689
2. Tracker ticket: https://tracker.ceph.com/issues/63993
--
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
Hey all,
Crimson's main goal for '23 was completing snapshots, scrub and
establishing a functional test suite. With the current status of supporting
RBD workloads on replicated pools with a stable test coverage - we are
ready now to move on to the next phase.
As Crimson's main objective is to allow Ceph to keep up with highly
performant network and storage devices, the next goal will be a concerted
performance focus.
Great progress around this area has already begun by Intel's contributors
and others [1], the collaboration will continue with joint and renewed
efforts.
The first planned steps would be to create a performance baseline relative
to the classical OSD and investigate existing bottlenecks.
The new meeting to discuss the ongoing progress will happen on every
Tuesday, 7:30 am PT [2], right before Crimson's standup. Please feel free
to join!
For more information see: https://ceph.io/en/news/crimson/ or join our
Slack channel #crimson in ceph-storage.slack.com.
Thank you,
Matan Breizman
[1] Crimson-Perf PRs
<https://github.com/ceph/ceph/pulls?q=is%3Apr+label%3Acrimson-perf+>
[2] Community Calendar meeting
<https://www.google.com/calendar/event?eid=NWtzNW45cmo0OW01Z3JmdDlpYjNrMzZyc…>
Hi Folks,
Happy new year! Today we'll talk about a long standing performance
issue on our ubuntu builds and memory consumption in the pglog seemingly
due to a large number of osdmaps and per-pglog entry rollback data.
Please feel free to add your own topic as well!
Etherpad:
https://pad.ceph.com/p/performance_weekly
Meeting URL:
https://meet.jit.si/ceph-performance
Mark
--
Best Regards,
Mark Nelson
Head of R&D (USA)
Clyso GmbH
p: +49 89 21552391 12
a: Loristraße 8 | 80335 München | Germany
w: https://clyso.com | e: mark.nelson(a)clyso.com
We are hiring: https://www.clyso.com/jobs/
Happy 2024!
Today's CLT meeting covered the following:
1. 2024 brings a focus on performance of Crimson (some information here: https://docs.ceph.com/en/reef/dev/crimson/crimson/ )
1. Status is available here: https://github.com/ceph/ceph.io/pull/635
2. There will be a new Crimson performance weekly meeting that will be lead by Matan Breizman
1. This does not replace the existing performance weekly, and is focused on Crimson
2. An email will follow with more details about this meeting
2. Ceph Quarterly will be published on/around the 14th of January, 2024.
1. See https://ceph.io/en/community/cq/ for previous issues of CQ
3. A development freeze on Squid is tentatively scheduled for January 31, 2024
4. Upcoming releases
1. 16.2.15 is next (the last Pacific release)
1. Anticipated by the end of January
2. 17.2.8 will follow (Quincy)
3. 18.2.2 will follow this (Reef)
