Anthony and Adam mostly covered it, but I have a few small things to add. On Thursday, May 15, 2025 12:13:21 PM Eastern Daylight Time Anthony D'Atri wrote: > > On May 15, 2025, at 1:22 AM, Florent Carli <[email protected]> wrote: > > > > Hello ceph team, [... snip ...] > > > > > 2) Containerization vs. local dependencies > > > > Cephadm’s move to full containerization makes sense in principle, > > especially to avoid system-level dependencies. > > > This is so, so, so nice. It also greatly facilitates the orchestrator’s > ability to move daemons around. > > > However, in practice, > > many operations (e.g., using ceph-bluestore-tool > > > Using that tool, to be fair, should be rare. Notably that tool requires > that the OSD on which it operates not be running. I would think it might > be possible to enter an OSD container and kill the ceph-osd process without > killing the container so that the tool could be run there, but there might > not be other processes in OSD containers so that may be a non-starter. > > > or the python modules for Rados/rbd) > > > I’m not familiar with those. >
It depends a bit on what you're doing with these modules. Are you using them interactively in a python prompt or are you building applications on top of them? For the former, Adam's other response mostly covers it: use cephadm shell and then the libraries will be present and available for import. If you're building applications with these libraries then you do have a choice to make. You can continue to install packages as dependencies (as you note there are some issues with that) or you can build your applications into a container image of your own, potentially based on the ceph image(s), and then invoke your application as a container. There's a bit of a hacky middle-ground in that you can invoke cephadm shell with a additional volume and if that volume contains your application code, you could try running your code from that volume within the container. > > > 3) Ceph packages for Debian Trixie on download.ceph.com > > > > Since I'm using debian, I'm also in the process of anticipating the > > soon to come Debian 13 version (Trixie). > > > I can’t speak authoritatively for the build folks, but you do note that this > is incipient. It’s not unusual for support for a new OS release to take > some time for any given software, and for enterprises to let a new major OS > release to bake / shakeout for a while before betting the farm on it. As > David Lindley wrote, “Rasta soon come”. > _______________________________________________ > ceph-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
