On Tue, Aug 28, 2012 at 5:03 PM, Florian Haas <florian@xxxxxxxxxxx> wrote: > I for my part, in the documentation space, would love for the admin > tools to become self-documenting. For example, I would love a "help" > subcommand at any level of the ceph shell, listing the supported > subcommands in that level. As in "ceph help", "ceph mon help", "ceph osd > getmap help". > > Even better, the ceph shell could support a general-purpose hook that > bash-completion can use (kind of like "hg" does in Mercurial), and this > and the above-conjectured help facility could arguably share quite a bit > of code. I would love to see all of that. But, a lot of the "ceph" tool functionality is implemented by shoveling strings in and out of the monitors. It largely doesn't understand what's happening. If we were to redo that from scratch, I'd convert that to have some sort of API to monitors, and make the cli understand all the relevant things. Understandably, that can feel a little bit more rigid; to add a command means adding it to both the server and a client, where as currently the client is very very generic. >> and also integration with CM like puppet/chef > +1, although people are already working on both. So maybe this is just > about the need to tell more people about that. :) Please do give constructive feedback on http://ceph.com/docs/master/install/chef/ http://ceph.com/docs/master/config-cluster/chef/ -- 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
