Hi all, In discussion with Noah about using the inter-module calls[1], we got to thinking about whether we now need a dependency concept between modules. However, maybe we can avoid doing full-on dependency management -- when there is a hard dependency, it's generally on an "infrastructure" type module (like "crash" or "progress"). Since those modules don't e.g. depend on external libraries or do external IO, it would be possible to simply always enable them on all systems. This would also simplify: - upgrades, where currently people don't get the new modules unless they explicitly enable them. - documentation, where functionality in an "always on " module wouldn't need to be caveated with instructions for enabling it, as the user wouldn't even notice that the functionality was coming from a mgr module. So, any thoughts on this? Should we add an "always on" flag to MgrModule? If we have it, is that going to be sufficient to avoid needing any more complex dependency management between modules? Cheers, John 1. https://github.com/ceph/ceph/pull/22951 -- 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
