From: Guido Winkelmann <guido-ceph@thisisnotatest.de>
To: elder@inktank.com, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: RBD layering design draft
Date: Fri, 22 Jun 2012 16:37:12 +0200 [thread overview]
Message-ID: <2294446.qgV7dgiTVM@pc10> (raw)
In-Reply-To: <4FE3976C.5000508@dreamhost.com>
> On 06/15/2012 03:48 PM, Josh Durgin wrote:
> > Then you can perform the clone:
> > $ rbd clone --parent pool/parent@snap pool2/child1
>
> Based on my comments above, if the parent had not been "preserved"
> it would automatically be at this point, by virtue of the fact it
> has a clone associated with it.
>
> Since there is always exactly one parent and one child, I'd say
> drop the "--parent" and just have the parent and child be
> defined by their position. If the parent could be optionally
> skipped for some reason, then make it be the second one.
I think that would be a very bad idea. clone <source> <target> would be a good
idea; nearly all similar commandline utilities (cp, mv, ln) work like that.
clone <target> <source> would be counterintuitive and probably lead to
otherwise avoidable mistakes.
Guido
next prev parent reply other threads:[~2012-06-22 14:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 20:48 RBD layering design draft Josh Durgin
2012-06-16 0:46 ` Sage Weil
2012-06-16 2:00 ` Yehuda Sadeh
2012-06-16 15:11 ` Sage Weil
2012-06-17 13:42 ` Martin Mailand
2012-06-18 18:04 ` Gregory Farnum
2012-06-18 16:25 ` Tommi Virtanen
2012-06-18 23:10 ` Dan Mick
2012-06-18 17:00 ` Tommi Virtanen
2012-06-18 17:14 ` Josh Durgin
2012-06-18 18:01 ` Sage Weil
2012-06-18 23:07 ` Dan Mick
2012-06-22 2:02 ` Alex Elsayed
2012-06-22 14:41 ` Guido Winkelmann
2012-06-22 14:36 ` Guido Winkelmann
2012-06-22 16:00 ` Tommi Virtanen
2012-06-21 21:51 ` Alex Elder
2012-06-22 14:37 ` Guido Winkelmann [this message]
2012-06-22 16:27 ` Tommi Virtanen
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=2294446.qgV7dgiTVM@pc10 \
--to=guido-ceph@thisisnotatest.de \
--cc=ceph-devel@vger.kernel.org \
--cc=elder@inktank.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