On Tue, Jun 28, 2016 at 8:54 PM, Lars Marowsky-Bree <lmb@xxxxxxxx> wrote: > Hi all, > > silly question time. From a UX perspective, we sometimes need to know > what a specific pool does. We can't always figure it out directly by > looking at the pool - is this used for RBDs? A MDS metadata pool? RGW > buckets? > > Right now, that is all bundled into the naming scheme. Is that the way > to proceed? Is there a recommended/standard naming scheme that tools > could attach to, then? > > We though of storing it in an object in the pool, but, uh, that > obviously doesn't work so well for cache-tiered pools ;-) > > Or should we have metadata about our Ceph entities maintained outside > Ceph, in a separate tooling database? > > Or would there be the chance to somehow store some description > somewhere, like a few k/v, free-form? x-... parameters maybe? (/me perfoms arcane ritual to bring this thread back from the grave) I'm wondering if Lars or anyone else went further with the pool metadata topic at all? Aside from the integration with external tools, I'm finding that I would also use this for sanity-checking pool selection within Ceph itself. e.g. I would like rbd pools to be marked as such, so that if I'm offering the user a list of pools to use with cephfs then I can exclude the rbd ones, and the same for rgw. John > (Tool suppliers could then agree on common tags, hopefully.) > > > > Regards > Lars > > -- > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) > "Experience is the name everyone gives to their mistakes." -- Oscar Wilde > > -- > 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 -- 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
