> > On Thu, Oct 5, 2017 at 7:45 PM, Alex Gorbachev <ag@xxxxxxxxxxxxxxxxxxx> wrote: >> I am testing rbd mirroring, and have two existing clusters named ceph >> in their ceph.conf. Each cluster has a separate fsid. On one >> cluster, I renamed ceph.conf into remote-mirror.conf and >> ceph.client.admin.keyring to remote-mirror.client.admin.keyring, but >> it looks like this is not sufficient: >> >> root@lab2-mon3:/etc/ceph# rbd --cluster remote-mirror mirror pool peer >> add spin2 client.admin@remote-mirror >> rbd: error adding mirror peer >> 2017-10-05 19:40:52.003289 7f290935c100 -1 librbd: Cannot add self as >> remote peer >> >> Short of creating a whole new cluster, are there any options to make >> such configuration work? On Thu, Oct 5, 2017 at 8:13 PM, Jason Dillaman <jdillama@xxxxxxxxxx> wrote: > The "cluster" name is really just the name of the configuration file. > The only issue with your command-line is that you should connect to > the "local" cluster to add a peer as a remote cluster: > > rbd --cluster ceph mirror pool peer add spin2 client.admin@remote-mirror Thank you Jason, works perfectly now. I used this link to get a bit of context on local vs. remote https://cloud.garr.it/support/kb/ceph/ceph-enabling-rbd-mirror/ Summary: It's OK to have both local and remote clusters named ceph, just need to copy and rename the .conf and keyring files. Best regards, Alex _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com