Den ons 10 okt. 2018 kl 16:20 skrev John Spray <jspray@xxxxxxxxxx>: > So the question is: does anyone actually use this feature? It's not > particularly expensive to maintain, but it might be nice to have one > less path through the code if this is entirely unused. It can go as far as I am concerned too. Better spend time on making the verbose flag do better that just listing the 189 sub-commands you didn't use and then have more or less the same output as if you ran without --verbose. (try 'ceph status' -vs- 'ceph status --verbose' for instance) In the cases where it actually needs to perform things, talk network and such things and fails it would be helpful if those messages didn't drown in all that "this ceph status wasn't ceph osd crush reweight and not ceph pg dump and not ..." I get that someone wanted to debug the parser once, but that could be some other flag than "the admin wants to know the substeps this command tries so the fault can be found when it doesn't work" which --verbose flags tend to try to be in other software. -- May the most significant bit of your life be positive.
