On Thu, 8 Jun 2017, Sage Weil wrote: > Questions: > > - Does anybody on the list use a non-default cluster name? > - If so, do you have a reason not to switch back to 'ceph'? It sounds like the answer is "yes," but not for daemons. Several users use it on the client side to connect to multiple clusters from the same host. Nobody is colocating multiple daemons from different clusters on the same host. Some have in the past but stopped. If they choose to in the future, they can customize the systemd units themselves. The rbd-mirror daemon has a similar requirement to talk to multiple clusters as a client. This makes me conclude our current path is fine: - leave existing --cluster infrastructure in place in the ceph code, but - remove support for deploying daemons with custom cluster names from the deployment tools. This neatly avoids the systemd limitations for all but the most adventuresome admins and avoid the more common case of an admin falling into the "oh, I can name my cluster? cool! [...] oh, i have to add --cluster rover to every command? ick!" trap. sage _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |