All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Buck <joe.buck@inktank.com>
To: christophe courtaut <christophe.courtaut@gmail.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Radosgw-agent data full sync implementation
Date: Wed, 28 Aug 2013 22:04:47 -0700	[thread overview]
Message-ID: <521ED66F.8020705@inktank.com> (raw)
In-Reply-To: <CAA8043h7rzRzmNfBex6p9g5t9VGsH4Ln=VNZzxJf3OpquPHZKA@mail.gmail.com>

On 08/28/2013 09:21 AM, christophe courtaut wrote:

> Hi Joe,
>
> I'm currently looking at the radosgw-agent, and i have seen your
> recent job on full sync of data.
>
> What will be the preferred way to list all objects to sync? Using
> admin API or standard S3 API?

It looks like we'll use the S3 API to list the objects in a bucket
(we'll actually use the boto library to do this).
It's worth noting that there's some locking that we need to do to
account for multiple agents running at the same time, so it's not quite
as easy as "list objects, sync objects, call it a day".

> Moreover, we will need to do an exact copy of the object to preserve
> attributes, as mentionned here
> http://pad.ceph.com/p/rgw-multi-region-dr  .
>
> Will this be part of the admin API? or am i missing something?

The following link on the wiki has most (all?) of the calls that are
being added for the sync work. There's an extended object GET and PUT in
there, towards the top.
http://wiki.ceph.com/index.php?title=RESTful_API_for_DR_%2F%2F_Geo-Replication
This link is also handy in terms of an overview:
http://www.spinics.net/lists/ceph-devel/msg11905.html

> Btw i recently posted an article here :http://blog.kri5.fr/?p=21, to
> setup two cluster for testing purpose of the radosgw-agent.

Cool.

> Best regards.
>

      reply	other threads:[~2013-08-29  5:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 16:21 Radosgw-agent data full sync implementation christophe courtaut
2013-08-29  5:04 ` Joe Buck [this message]

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=521ED66F.8020705@inktank.com \
    --to=joe.buck@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=christophe.courtaut@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.