On Wed, Feb 23, 2011 at 2:13 PM, Tommi Virtanen <tommi.virtanen@xxxxxxxxxxxxx> wrote: > On Wed, Feb 23, 2011 at 01:58:19PM -0800, Colin Patrick McCabe wrote: >> *** g_conf.id: this is a username or a daemon name, depending on the program. >> It defaults to "admin" for our various command-line tools, but can be >> changed by the -i command-line argument. >> For an MDS, this would be "a" or "b", or similar. > > Noob question: why not 0, 1, ..? You're not the only one to ask why OSDs are osd.0, osd.1, etc., whereas MDSes are mds.a, mds.b, etc. I think the reasons are historical. > >> *** g_conf.type: nobody seems to know what this is. >> It seems like at one point, g_conf.type was intended to be one of >> "auth", "mon", "osd", "mds", or "client". > > This seems to be tied to cconf's use of "type" as in sections "osd0" > and "osd.0" are both type=osd, id=0. So, it soudns to be like it's > there mostly to get around the fact that config section names are not > predictable. When filling out a configuration section for the first OSD, you can use either "osd.0" or "osd0" as the section name. This is kind of an obscure configuration quirk, though. My point was that g_conf.type is redundant since we have the same info in a nicely parsed form in g_conf.entity_name. (There's no reason we can't continue to support the quirky no-period syntax either.) Colin -- 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
