Hello ceph team, I’ve been working with ceph for some time and am currently evaluating cephadm as a successor to ceph-ansible. During this process, I’ve encountered a few aspects of the cephadm approach that raised some questions, and I’d greatly appreciate your insights to better understand the intended usage and philosophy.
1) Declarative workflows and Infrastructure as Code One of the advantages of ceph-ansible was the ability to define the cluster state declaratively in YAML files, which aligned well with Infrastructure-as-Code principles. With cephadm, the process appears more imperative and CLI-driven, which makes automation and reproducibility harder in comparison. Is there a recommended approach to achieving a fully declarative deployment model with cephadm? Or plans to support this more directly? 2) Containerization vs. local dependencies Cephadm’s move to full containerization makes sense in principle, especially to avoid system-level dependencies. However, in practice, many operations (e.g., using ceph-bluestore-tool, or the python modules for Rados/rbd) still seem to require installing packages on the host. Is this the expected model : containers for core daemons, but local packages for tooling ? It feels somewhat contradictory, and I wonder if there's a clearer pattern or guidance for those cases. 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). "cephadm install" pulls packages from download.ceph.com, where the latest versions are published. Currently, it seems that there are no ceph packages yet for Trixie on download.ceph.com, which forces me to use the debian hosted packages (they are not even the same ceph version). Is there an ETA for when those packages will be made available? Or maybe there's another url for development packages? Thank you very much for your time and for your work on cephadm. I’m looking to better align our automation practices with the direction Cephadm is taking, and any clarification you can provide would be very helpful. Best regards, Florent. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
