At the risk of pedantry, I’d like to make a distinction, because this has
tripped people up in the past.
Cluster names and config file names are two different things. It’s easy to
conflate them, which has caused some people a lot of technical debt and grief.
Especially with `rbd-mirror`.
Hello Mosharaf,
yes, that's no problem. On all of my clusters I did not have a ceph.conf
in in the /etc/ceph folders on my nodes at all.
I have a .conf, .conf,
.conf ...
configuration file in the /etc/ceph folder. One config file for each
cluster.
The same for the different key files e.g.
Hello Markus
Thank you for your direction.
I would like to let you know that the way you show it is quite meaningful
but I am afraid how the ceph system would identify the configuration file
as by default it uses ceph. conf in /etc/ceph folder. Can we define the
config file as we want?
It will be
Hello,
yes you can use a single server to operate multiple clusters.
I have a configuration running, with two independent ceph clusters
running on the same node (of course multiple nodes for the two clusters)
The trick is to work with multiple ceph.conf files, I use two
seperate ceph.conf files
> Hi ciphers,
>
> We have two ceph clusters in our lab. We are experimenting to use single
> server as a client for two ceph clusters. Can we use the same client server
> to store keyring for different clusters in ceph.conf file.
The keys are usually in their own files in /etc/ceph, not in
