From: Jeff Wu <cpwu@tnsoft.com.cn>
To: Tommi Virtanen <tommi.virtanen@dreamhost.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Could rados pool support tree view feature ?
Date: Tue, 20 Dec 2011 09:47:58 +0800 [thread overview]
Message-ID: <1324345678.4089.35.camel@cephclient0> (raw)
In-Reply-To: <CAORUGqD5yJyzDNmVRa5jaj54hF-JJU1UCqyNw5OAAhE4hHK8pQ@mail.gmail.com>
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@tnsoft.com.cn> 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@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-12-20 1:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 6:51 Could rados pool support tree view feature ? Jeff Wu
2011-12-19 17:16 ` Tommi Virtanen
2011-12-20 1:47 ` Jeff Wu [this message]
2011-12-20 6:38 ` Gregory Farnum
2011-12-20 8:57 ` Jeff Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1324345678.4089.35.camel@cephclient0 \
--to=cpwu@tnsoft.com.cn \
--cc=ceph-devel@vger.kernel.org \
--cc=tommi.virtanen@dreamhost.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox