On Tue, Feb 20, 2018 at 2:49 PM, Yehuda Sadeh-Weinraub
<yehuda@xxxxxxxxxx> wrote:
> On Tue, Feb 20, 2018 at 2:32 PM, Kyle Bader <kyle.bader@xxxxxxxxx> wrote:
>> The current unidirectional sync is:
>>
>> many buckets -> single bucket
>
> Not necessarily, depending on how it is configured.
Oh, cool!
>> What does that look like if we throw it in reverse?
>
> Depending how the configuration is going to look like. Generally there
> are a few params that deal with mutating the destination bucket/object
> name, and I think we can do some kind of reverse mapping too.
> Currently with the cloud sync you can specify different mappings for
> different buckets (or bucket prefixes). The mapping is defined by a
> configurable field that uses multiple variables to generate the remote
> bucket/object pair. These variables include the sync instance id,
> source zonegroup, source zone, source bucket name, and the bucket
> owner. The default destination name configuration is currently:
> "rgw-${zonegroup}-${sid}/${bucket}", but it can be set to anything
> (that is valid). A bucket named foo in zonegroup named zg with object
> named bar with sync instance id 100 will end up as: rgw-zg-100/foo/bar
> (that is bucket named rgw-zg-100, and object named foo/bar). But you
> could define a different mapping for any bucket, potentially have a
> 1:1 mapping between source buckets and destination buckets. One major
> problem is that in general you're very limited in the number of
> buckets you can create at the destination.
Yeah, AWS is a stickler on this. Generally speaking I don't think they
allow you to go beyond 1k buckets, even if you write in to their
support.
If you have a 1:1 mapping, can you provide different credentials for each map?
--
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
