> Hi. > > From our point of view, it's important to keep disk failure prediction tool as part of Ceph, ideally as an MGR module > . In environments with hundreds or thousands of disks, it's crucial to know whether, for example, a significant number of them are likely to fail within a month - which, in the best-case scenario, would mean performance degradation, and in the worst-case, data loss. Agreed, but the current implementation does not achieve this. > Some have already responded to the deprecation of diskprediction by starting to develop their own solutions. For instance, just yesterday, Daniel Persson published a solution [1] Videos and costumes aren’t solutions. > on his website that addresses the same problem. > > Would it be possible to join forces Are you volunteering to code? Can you sign up to be involved going forward? Ceph has suffered time and again from something being partly implemented, only to have the sole proponent wander away. > and try to revive that module? It really needs to be reimplemented in a less opaque way so that admins can contribute and tweak. No binary blobs. > > [1] https://www.youtube.com/watch?v=Gr_GtC9dcMQ > > Thanks, > Michal > > > On 4/8/25 01:18, Yaarit Hatuka wrote: >> Hi everyone, >> On today's Ceph Steering Committee call we discussed the idea of removing >> the diskprediction_local mgr module, as the current prediction model is >> obsolete and not maintained. >> We would like to gather feedback from the community about the usage of this >> module, and find out if anyone is interested in maintaining it. >> Thanks, >> Yaarit >> _______________________________________________ >> ceph-users mailing list -- ceph-users@xxxxxxx >> To unsubscribe send an email to ceph-users-leave@xxxxxxx > > > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |