2018-04-27 17:33 GMT+02:00 Sean Purdy <s.purdy@xxxxxxxxxxxxxxxx>:
Mimic has a new feature, a cloud sync module for radosgw to sync objects to some other S3-compatible destination.
This would be a lovely thing to have here, and ties in nicely with object versioning and DR. But I am put off by confusion and complexity with the whole multisite/realm/zone group/zone thing, and the docs aren't very forgiving, including a recommendation to delete all your data!
Is there a straightforward way to set up the additional zone for a sync module with a preexisting bucket? Whether it's the elasticsearch metadata search or the cloud replication, setting up sync modules on your *current* buckets must be a FAQ or at least frequently desired option.
Amen to "docs are very much lacking".
I tried to make buckets end up on different pools (== diff. disks) and had to fumble around the docs to (try to) understand at which level to make the split that makes some data end up and X and some at Y. The docs seemed to me to be focused just on synching, and not on "place client Xs data here" or "let client choose location" or something which would suit me. When we upgraded from Hammer/Infernalis to Jewel we just made Zonegroups and stuff to make S3 work at all, but no docs really tell me what the new separation levels are for so that I may edit the right place.
The blogs that did somewhat point to my usecase was from when it still had realms. 8-(
May the most significant bit of your life be positive.
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
