We use Ceph RBD/FS extensively and are starting down our RGW journey. We have 3 sites and want to replicate buckets from a single "primary" to multiple "backup" sites. Each site has a Ceph cluster and they are all configured as part of a Multisite setup. I am using the examples at https://docs.ceph.com/en/quincy/radosgw/multisite-sync-policy and have gotten a directional sync to work using the below commands. The question I have is about the scalability of what I am doing. How groups/flows/pipe all fit together is not very clear in the docs. My group 'us' has two flows, 'dev1-to-dev2' and 'dev1-to-dev3'. The pipe that I create specifies the group 'us' but does not specify the flows to us. I have to assume in this case it uses all of the flows at the zonegroup level. This is fine as long as these are the only flows that I will ever need. What I am try having difficulty understanding is the linkage between pipes and flows. If any one can explain this more than the docs do, it would be greatly appreciated. BTW: The Multisite Sync Policy docs are, IMHO, the most opaque/confusing section on the doc site overall. Setup: Version: 16.2.10 Clusters: 3 Zonegroup: us Zones: us-dev-1, us-dev-2, us-dev-3 Tenant: elvis Bucket: artifact radosgw-admin sync group create \ --group-id=us \ --status=allowed radosgw-admin sync group flow create \ --group-id=us \ --flow-id=dev1-to-dev2 \ --flow-type=directional \ --source-zone=us-dev-1 \ --dest-zone=us-dev-2 radosgw-admin sync group flow create \ --group-id=us \ --flow-id=dev1-to-dev3 \ --flow-type=directional \ --source-zone=us-dev-1 \ --dest-zone=us-dev-3 radosgw-admin sync group pipe create \ --group-id=us \ --pipe-id=systems-artifact \ --source-zones='us-dev-1' \ --source-bucket='elvis/artifact' \ --dest-zones='us-dev-2,us-dev-3' \ --dest-bucket='elvis/artifact' radosgw-admin sync group modify \ --group-id=us \ --status=enabled radosgw-admin period update --commit -- Mark Selby Sr Linux Administrator, The Voleon Group mselby@xxxxxxxxxx This email is subject to important conditions and disclosures that are listed on this web page: https://voleon.com/disclaimer/.
_______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
