On Mon, Jul 16, 2018 at 10:39 AM, Nathan Cutler <ncutler@xxxxxxx> wrote: >>> The upside is that I think the orchestrator mgr layer we're building >>> provides the right set of tools to build this pretty easily. Doing it >>> there means it can work equally well (with an identical user experience) >>> with ansible, rook, deapsea, whatever. >> >> >> Putting it in the mgr also would allow us to do things like scheduling >> time of day to do replacements, or maybe adjust recovery throttling >> automatically, or whatever else we decide would improve the overall >> process. > > > +1 to putting features in mgr if that lets us avoid having as many different > implementations of those features as there are orchestration tools. BTW I am not saying to *not* put it there, I am mostly interested in finding what are the gaps that ceph-volume can help, like mounting/unmounting, systemd, dmcrypt, etc... > > Nathan > > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
