Hi Travis, It seems there is a push towards being able to run Ceph tooling without a configuration file (usually in /etc/ceph/ceph.conf) [0]. I believe the reference ticket may be coming from a rook need, do you foresee rook being more of a "source of truth" for more operations in a Ceph cluster? My concern is how other tools would be able to interact with a Ceph cluster that may have some information in a separate system like rook. In the case of inspecting clusters, tools like ceph-medic poke around things that might be of interesting like ceph.conf. As you know, we found an instance where a ceph-mgr pod in rook didn't define its cluster fsid [1], and although that might not cause any issues, it was able to detect a problem because that pod was different from the other pods in the cluster. In short (and more towards Ceph in general) it would be good to normalize the way clusters operate, so that tooling will not have to try multiple sources for fetching information/configuration. Right now we have some items in the Monitors, but we allow config files (and multiple config files at that!) which is already tricky to get right. -Alfredo [0] http://tracker.ceph.com/issues/38279 [1] https://github.com/rook/rook/issues/2628
