On 23-04-16 18:17, Yehuda Sadeh-Weinraub wrote: > On Sat, Apr 23, 2016 at 6:22 AM, Richard Chan > <richard@xxxxxxxxxxxxxxxxxxxx> wrote: >> Hi Cephers, >> >> I upgraded to Jewel and noted the is massive radosgw multisite rework >> in the release notes. >> >> Can Jewel radosgw be configured to present existing Hammer buckets? >> On a test system, jewel didn't recognise my Hammer buckets; >> >> Hammer used pools .rgw.* >> Jewel created by default: .rgw.root and default.rgw* >> >> >> > Yes, jewel should be able to read hammer buckets. If it detects that > there's an old config, it should migrate existing setup into the new > config. It seemsthat something didn't work as expected here. One way > to fix it would be to create a new zone and set its pools to point at > the old config's pools. We'll need to figure out what went wrong > though. > Hi, I'm also wandering about the correct upgrade procedure for the radosgw's, especially in a multi gateway setup in a federated config. If you say existing setup should migrate, is it ok then to have hammer and jewel radosgw's co-exist (for a short time)? We have for example multi radosgw instances behind an haproxy. Can they be upgraded one at a time or do they all need to be stopped before starting the first jewel radosgw? Does the ceph.conf file needs to be adapted to the jewel config, fe change "rgw region root pool" into "rgw zonegroup root pool"? Before or after the upgrade? Concerning data replication. I understand the radosgw-agent is deprecated in jewel and the replication is done by the radosgw's them selves. Is this also automatically enabled or does this need to be started / configured somehow? thanks in advance, Sam _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |