In Rook there are changes in progress to bring the configuration of daemons more inline with what Ceph expects. Rook in the past has done most everything through the ceph.conf. Now the movement is away from ceph.conf, to use command line parameters where possible and mon settings for everything else. This is based on the understanding that ceph.conf is less preferred going forward. This is based on conversations with Sage for the preferred configuration approach. As long as needed, Rook will still generate a config file where necessary, such as for c-v. The assumption was that c-v could take advantage of the config changes that other daemons are going through, or at least would move in the same direction. On Thu, Feb 14, 2019 at 5:34 AM Alfredo Deza <adeza@xxxxxxxxxx> wrote: > > 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
