Hey, I'm about to add rbd-mirror support to teh ssh orch and have a few questions after skimming doc/rbd/rbd-mirroring.rst The orchestrator thinks of service in terms of sets. Rook, for example, can scale the number of daemons up and down. I assume I want one set of daemons per peer cluster? Does the rbd-mirror daemon then service any rbd-mirroring-enabled pool that works with taht peer cluster? Or is there anything I can/should do to tell a particular rbd-mirror daemon to work on one pool or peer vs another? FWIW on the RGW side, the 'group' is a zone, and we're making the client ids hierarchical, like client.rgw.$zone.$id. And the config subsystem has been updated so that we pull optoins from global, client, client.rgw, client.rgw.$zone, and client.rgw.$zone.$id. In the rgw case, we 'config set client.rgw.$zone rgw_zone $zone', which ensures all those daemons are working on the right thing. We might be able/want to do something similar here? Thanks! sage _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
