Hi Adrian, just want to add some other facts to cephadm. I started with cephadm together with SUSE around 2017. At this time together with Sage the idea was to develop an orchestrator for ceph that can manage ceph packages and containers. Around 2019 the decision was made to remove this middle layer and only focus on container orchestration. When Red Hat stopped Ceph-Ansible's development and support, there was a long mailing thread here, and no one volunteered to officially continue it. Therefore, currently only Cephadm and Rook are officially supported open-source Ceph orchestrators. Note: I happen to be at the KCD conference at CERN in December, if you have any more questions. Joachim joachim.kraftmayer@clyso.com www.clyso.com Hohenzollernstr. 27, 80801 Munich Utting | HR: Augsburg | HRB: 25866 | USt. ID-Nr.: DE275430677 Am Do., 20. Nov. 2025 um 07:18 Uhr schrieb Adrian Sevcenco < Adrian.Sevcenco@cern.ch>:
Hi! Is there any possibility to use cephadm without the container based tooling? (so to use bare-metal, with the packages directly installed on the machine)
If not, is there something technical that prevents it to happen or just that there is a policy that container based deployment is the only best way to do it therefore cephadm will only use it this way?
I ask this in the context of finding out that ceph-ansible is deprecated and that it should not be used, but i still need to use ansible for management and i think (so without factual experience) that bare metal services would be easier to manage after doing by hand deployment with cephadm
Thank you! Adrian _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io