Hi, while your assumptions are correct (you can use the rest of the pool for other non-mirrored images), at least I'm not aware of any limitations, can I ask for the motivation behind this question? Mixing different use-cases doesn't seem like a good idea to me. There's always a chance that a client with caps for that pool deletes or modifies images or even the entire pool. Why not simply create a different pool and separate those clients? Thanks, Eugen Zitat von wodel youchi <wodel.youchi@gmail.com>:
Hi,
When using rbd mirroring, the mirroring concerns the images only, not the whole pool? So, we don't need to have a dedicated pool in the destination site to be mirrored, the only obligation is that the mirrored pools must have the same name.
In other words, We create two pools with the same name, one on the source site the other on the destination site, we create the mirror link (one way or two ways replication), then we choose what images to sync.
Both pools can be used simultaneously on both sites, it's the mirrored images that cannot be used simultaneously, only promoted ones.
Is this correct?
Regards. _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io