>> >> Hence the increasing motivations for container installations, which are >> by nature immune from this dynamic. >> > > I don't know about that, you just move the issue from ceph daemons to > container daemons.
Daemons have individual container images that are updated individually, which obviates the issue. > If I remember correctly, I even read something here on the list about podman > version problems there. With recent OS, Ceph, and Podman releases this is moot. > And since a lot is going still via hosts configs not volumes assigned to the > task, changes between the host and the task image could also complicate > things. Didn't I read recently something with lvm.conf or so? > > >>> I would expect ceph to be more robust. >> >> It's not a function of Ceph, but robustness is exactly the goal. > > So what is then all this nonsense of having a minor upgrade on a node? I have > never seen any issues with apache httpd, mariadb, postgres etc. Nor with ceph > for that matter. ymmv. _______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
