On Mon, 11 Feb 2013, Gregory Farnum wrote: > [...] > ...but my instinct is to want one canonical code path in the monitors, > not two. Two allows for discrepancies in what each method allows to > [...] Yeah, I'm convinced. Just chatted with Dan and Josh a bit about this. Josh had the interesting idea that the specification of what commands are supported could be requested from the monitor is some canonical form (say, a blob of JSON), and then enforced at the client. That would be translated into an argparse config for the CLI, and a simple matching/validation table for the REST endpoint. That might be worth the complexity to get the best of both worlds... but first Dan is looking at whether Python's argparse will do everything we want for the CLI end of things. In the meantime, the first set of tasks still stand: move the ceph tool cruft into MonClient and Objecter and out of tool/common.cc for starters. sage -- 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
