On 11/20/25 7:03 AM, Burkhard Linke wrote:
Hi,
On 11/20/25 07:17, Adrian Sevcenco wrote:
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
Just my 0.02 euro:
I'm not exactly a fan of containers for critical infrastructure, and
adding another layer to an already complex system is not making your
life easier. Our clusters are still running on bare metal and manual /
ansible based deployment, but we will probably change this with Tentacle.
There's a simple reason for it: choice.
With a container based approach, it doesn't matter which linux
distribution and which exact release you want to use. And the subtle
differences between distribution, slightly varying library packages
etc. makes the life of a developer really hard. This is were
containers shine. You build them once with the distribution that fits
your needs, and do not care about the deployment on the hosts.
Container just works[tm].
Thus displacing the problem from developers to the admins as now admins
have to maintain the whole container support environment, including the
"slightly varying library packages etc." This whole exercise is
pointless as Ceph cluster storage nodes are natively dedicated to Ceph,
thus the bare-metal machine is the real Ceph container. Just install the
specific OS supported by Ceph and you've got your Ceph "container" made
out of metal.
You can make an argument that monitor and/or manager daemons could run
in containers to allow for migration to alternative nodes. Properly
sized Ceph clusters come with a number of dedicated monitor nodes
anyway, therefore migration usually means add a new monitor node to the
cluster and remove the old one, thus making the monitor containers point
moot, too.
Milan
--
Milan Kupcevic
Research Computing Lead Storage Engineer
Harvard University
HUIT, University Research Computing
_______________________________________________
ceph-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
