Because all of this reads way to negative regarding containers for me I
wanted to give a different perspective.
Coming from a day to day job, that heavily utilizes kubernetes for its
normal environment, I found cephadm quite like a godsent,
instead of having to deal with a lot of pesky
> 3. Why is in this cephadm still being talked about systemd? Your orchestrator
> should handle restarts,namespaces and failed tasks not? There should be no
> need to have a systemd dependency, at least I have not seen any container
> images relying on this.
Podman uses systemd to manage
Thanks for answering these. I have been using ceph since Kraken and are now on
Nautilus. I thought before to join this discussion to watch this video[1] on
cephadm, but it seems to be more about what console commands to type. So please
indulge my rookie comments.
> the cephadm
> team isn't
