Hi everyone,
On behalf of the Ceph Foundation Board, I would like to announce the
creation of, and cordially invite you to, the first of a recurring series
of meetings focused solely on gathering feedback from the users of
Ceph. The overarching goal of these meetings is to elicit feedback from the
users, companies, and organizations who use Ceph in their production
environments. You can find more details about the motivation behind this
effort in our user survey [1] that we highly encourage all of you to take.
This is an extension of the Ceph User Dev Meeting with concerted focus on
Performance (led by Vincent Hsu, IBM) and Orchestration/Deployment (led by
Matt Leonard, Bloomberg), to start off with. We would like to kick off this
series of meetings on March 21, 2024. The survey will be open until March
18, 2024.
Looking forward to hearing from you!
Thanks,
Neha
[1]
https://docs.google.com/forms/d/15aWxoG4wSQz7ziBaReVNYVv94jA0dSNQsDJGqmHCLM…
Hi folks,
As many of you are aware, RAM/CPU is particularly scarce on
teuthology.front.sepia.ceph.com which means that any log viewing of QA
results can cause swapping and general slowness. At today's Ceph
Infrastructure Weekly call [1], I proposed only allowing root,
www-data, and teuthworker access to /teuthology so that others would
be forced to look at logs on other beefier development machines like
senta [2], vossi [3], your personal workstation [4], or even some
temporary locked node [5].
The current plan is to proceed barring some reasonable justification
not to. There are a few to-do items to make it happen laid out in the
minutes.
Until then, admins of teuthology would appreciate it if you already
start moving your log viewing to other machines without waiting for a
technical barrier to be set up.
[1] https://pad.ceph.com/p/ceph-infra-weekly
[2] https://wiki.sepia.ceph.com/doku.php?id=hardware:senta
[3] https://wiki.sepia.ceph.com/doku.php?id=hardware:vossi
[4] https://wiki.sepia.ceph.com/doku.php?id=services:cephfs
[5] https://wiki.sepia.ceph.com/doku.php?id=testnodeaccess
--
Patrick Donnelly, Ph.D.
He / Him / His
Red Hat Partner Engineer
IBM, Inc.
GPG: 19F28A586F808C2402351B93C3301A3E258DD79D
this ceph-object-corpus repo is the basis of our ceph-dencoder test
src/test/encoding/readable.sh, which verifies that we can still decode
all of the data structures encoded by older ceph versions
i'd like to raise awareness that this ceph-object-corpus repo hasn't
been updated with new encodings since pacific 16.2.0, so we're missing
important regression test coverage since then
Nitzan prepared the encodings for reef 18.2.0 in
https://github.com/ceph/ceph-object-corpus/pull/17, but those haven't
merged yet. i had opened https://github.com/ceph/ceph/pull/54735 to
test that, but 'make check' identified failures like:
> The following tests FAILED:
> 147 - readable.sh (Failed)
>
> **** reencode of /home/jenkins-build/build/workspace/ceph-pull-requests/ceph-object-corpus/archive/18.2.0/objects/chunk_refs_t/ccb69d9ecd572c1f6ed9598899773cf1 resulted in a different dump ****
can we find a way to prioritize this? it would be great to have these
reef encodings while we're validating the squid release
Hello Ceph List,
I'd like to formally let the wider community know of some work I've been
involved with for a while now: adding Managed SMB Protocol Support to Ceph.
SMB being the well known network file protocol native to Windows systems and
supported by MacOS (and Linux). The other key word "managed" meaning
integrating with Ceph management tooling - in this particular case cephadm for
orchestration and eventually a new MGR module for managing SMB shares.
The effort is still in it's very early stages. We have a PR adding initial
support for Samba Containers to cephadm [1] and a prototype for an smb MGR
module [2]. We plan on using container images based on the samba-container
project [3] - a team I am already part of. What we're aiming for is a feature
set similar to the current NFS integration in Ceph, but with a focus on
bridging non-Linux/Unix clients to CephFS using a protocol built into those
systems.
A few major features we have planned include:
* Standalone servers (internally defined users/groups)
* Active Directory Domain Member Servers
* Clustered Samba support
* Exporting Samba stats via Prometheus metrics
* A `ceph` cli workflow loosely based on the nfs mgr module
I wanted to share this information in case there's wider community interest in
this effort. I'm happy to take your questions / thoughts / suggestions in this
email thread, via Ceph slack (or IRC), or feel free to attend a Ceph
Orchestration weekly meeting! I try regularly attend and we sometimes discuss
design aspects of the smb effort there. It's on the Ceph Community Calendar.
Thanks!
[1] - https://github.com/ceph/ceph/pull/55068
[2] - https://github.com/ceph/ceph/pull/56350
[3] - https://github.com/samba-in-kubernetes/samba-container/
Thanks for reading,
--John Mulligan
there was a consensus to drop support for ubuntu focal and centos
stream 8 with the squid release, and i'd love to remove those distros
from the shaman build matrix for squid and main branches asap
however, i see that quincy never supported ubuntu jammy, so our quincy
upgrade tests still have to run against focal. that means we'd still
have to build focal packages for squid
would it be possible to start building jammy packages for quincy to
allow those upgrade tests to run jammy instead?
this isn't an issue on the centos side because we've been building
centos 9 packages for quincy even though it's not listed in
https://docs.ceph.com/en/latest/start/os-recommendations/#platforms
Hi Guillaume,
We need to move the Squid release to use a CentOS Stream 9 image
instead of 8. (CentOS Stream 8 is EOL in a few months.)
We also want to move Ceph's Dockerfile
(https://github.com/ceph/ceph-container/issues/2171)
What is the next step to accomplish these goals?
There are multiple jobs that have been in the queue over ten hours without
starting to build
Which Jenkins version are we using? Jenkins 2.222.3, 2.205 or anything in
between have this issue where jobs are waiting for multiple hours without
starting to build. Using Jenkins 2.204.6 or earlier tends to solve this
issue.
Source:
https://issues.jenkins.io/projects/JENKINS/issues/JENKINS-61779?filter=allo…
Hi Folks,
The performance meeting will be cancelled tomorrow as I have a
conflict. I'll be giving a webinar on hitting 1 TiB/s with Ceph the
hour before and it may go over with the Q&A session. Please feel free to
join us at the webinar if you are interested instead however!
https://www.eventbrite.com/e/meet-the-experts-mark-nelson-presents-ceph-a-j…
Thanks,
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/