Hi all.
As we noted earlier, "rados get" and "rados put" do gets and puts,
respectively. This is different from "export" and "import" which have
always synchronized whole pools.
I guess we can have syntax like this for the import and export:
rados sync [import|export] <options> <src> <dst>
I will implement that in a branch called
wip-merge-radostool-with-radossync and you can evaluate whether you
like it better than having a separate binary or not.
Colin
On Mon, May 9, 2011 at 4:29 PM, Gregory Farnum
<gregory.farnum@xxxxxxxxxxxxx> wrote:
> On Mon, May 9, 2011 at 4:24 PM, Gregory Farnum
> <gregory.farnum@xxxxxxxxxxxxx> wrote:
>> Ermm, doesn't rados sync do a whole tree sync or something? I think we
>> want to maintain a simple get/set object capability and the rados tool
>> is a pretty logical place for that.
>> -Greg
> Sorry, Gmail got confused so I resent! :(
>
>
> On Mon, May 9, 2011 at 4:25 PM, Sage Weil <sage@xxxxxxxxxxxx> wrote:
>> On Mon, 9 May 2011, Gregory Farnum wrote:
>>> Ermm, doesn't rados sync do a whole tree sync or something? I think we
>>> want to maintain a simple get/set object capability and the rados tool
>>> is a pretty logical place for that.
>>
>> The main difference with sync is that it does incremental updates (skips
>> dup items).
>>
>> As an aside I we should move that into the rados tool, though ('rados
>> sync' instead of 'rados_sync')...
> If it's that simple a syntax change, I agree. I thought rados_sync
> would require an empty directory if you just want to pull an object
> out, which was my main concern.
> -Greg
> --
> 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
