Hi Greg , Thanks! Jeff On Tue, 2011-12-20 at 14:38 +0800, Gregory Farnum wrote: > Unfortunately pools are completely flat namespaces, and there's no > hierarchical relationship between pools (well, really it's a feature, > not something unfortunate). So any tree structure would need to be a > completely external thing, which I guess you would probably do with > naming conventions and some wrapper scripts. > -Greg > > On Mon, Dec 19, 2011 at 5:47 PM, Jeff Wu <cpwu@xxxxxxxxxxxxx> wrote: > > Hi ,Tommi > > Thank you very much. > > > > 00011 and 00012 are sub-pools ,we want to map our iaas devices topology > > view meta data to these these sub-pools as a reference model. > > > > On Tue, 2011-12-20 at 01:16 +0800, Tommi Virtanen wrote: > >> On Sun, Dec 18, 2011 at 22:51, Jeff Wu <cpwu@xxxxxxxxxxxxx> wrote: > >> > Could rados pool support tree view feature ?for instance : > >> > > >> > $rados lspools -m 172.16.10.10 > >> > data > >> > metadata > >> > rbd > >> > Product:00000001 > >> > ├── 00011 > >> > │ └── 00012 > >> > | └── 00013 > >> > >> What type are the 00011 and 00012 entries? Are they pools or objects, > >> or what? RADOS pools are flat namespaces of objects, there's no tree > >> structure there. > >> > >> You should be able to write that easily, for example less than 100 > >> lines of Python using the "rados" module gets you the listing of the > >> pools and the objects in them, and then you can use whatever your > >> custom logic is for creating that tree shape. > >> > >> The Ceph team pretty much starts with the assumption that your pools > >> are going to have at least millions of objects, so it's unlikely we'll > >> write pretty visual navigation apps listing individual objects. The > >> output would just be too long to be useful. > > > > -- > > 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