I know this doesnt answer your question directly but instead of bothering naming our clusters something other than ceph we name all of our clusters "ceph" and then just concern ourselves with creating the /etc/ceph/XXXX.conf and the /etc/ceph/XXX.client.user.keyring on our clients to differentiate one cluster from the other. This works well for our situation where only clients are "aware" of two clusters and helps us avoid the mucky situation of having non-standard cluster names - as that proved to be a real pain point for deployment. Good luck On Wed, Oct 12, 2016 at 3:18 AM, Jaze Lee <jazeltq@xxxxxxxxx> wrote: > If using systemd, we can not specific cluster name when active an osd... > Is there a way to send in the ENV CLUSTER by systemctl? > > > Thank a lot > > -- > 谦谦君子 > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Respectfully, Wes Dillingham wes_dillingham@xxxxxxxxxxx Research Computing | Infrastructure Engineer Harvard University | 38 Oxford Street, Cambridge, Ma 02138 | Room 210 -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
