On Wed, Sep 24, 2014 at 2:12 PM, Robin H. Johnson <robbat2 at gentoo.org> wrote: > On Wed, Sep 24, 2014 at 11:31:29AM -0700, Yehuda Sadeh wrote: >> On Wed, Sep 24, 2014 at 11:17 AM, Craig Lewis <clewis at centraldesktop.com> wrote: >> > Yehuda, are there any potential problems there? I'm wondering if duplicate >> > bucket names that don't have the same contents might cause problems? Would >> > the second cluster be read-only while replication is running? >> I might have missed part of the original requirements. This sync >> assumes that B starts as a clean slate. No writes are allowed to it >> while data is being copied into it. Once ready, all writes to A should >> be quiesced. Once sync completes, they would then need to reconfigure >> their system to make B the primary zone. > If my B side was empty, I would simply add all the OSDs in as a single > cluster. > > It's the there are S3 buckets & RBD images on both sides; none of the > bucket names or RBD images conflict, so I was hoping there was a way to > merge them. The sync agent might still work if there are no overlapping buckets. You'll need to add both clusters as zones in the same region, create a system user that will exist on both, and set the agent to do a full sync from A to B. The only thing I'm not sure is whether the sync agent will try to remove stuff from B as it doesn't exist on A. I don't think it'll do it, but it's better be safe than be sorry. Josh, do you see an issue there? Yehuda > > -- > Robin Hugh Johnson > Gentoo Linux: Developer, Infrastructure Lead > E-Mail : robbat2 at gentoo.org > GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 > _______________________________________________ > ceph-users mailing list > ceph-users at lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |