If you can move away from having a non-default cluster name, do that. It's honestly worth the hassle if it's early enough in your deployment. Otherwise you'll end up needing to symlink a lot of things to the default ceph name. Back when it was supported, we still needed to have /etc/ceph/ceph.conf symlinked to our actual config file for multiple ceph tools. It was never a widely adopted feature, and the nature open-source had a lot of people contributing tools that had never used or thought about clusters with different names.
On Fri, Apr 20, 2018 at 4:56 PM Robert Stanford <rstanford8...@gmail.com> wrote: > > Thanks Gregory. How much trouble I'd have saved if I'd only known this... > > On Fri, Apr 20, 2018 at 3:41 PM, Gregory Farnum <gfar...@redhat.com> > wrote: > >> Not sure about this specific issue, but I believe we've deprecated the >> use of cluster names due to (very) low usage and trouble reliably testing >> for all the little things like this. :/ >> -Greg >> >> On Fri, Apr 20, 2018 at 10:18 AM Robert Stanford <rstanford8...@gmail.com> >> wrote: >> >>> >>> If I use another cluster name (other than the default "ceph"), I've >>> learned that I have to create symlinks in /var/lib/ceph/osd/ with >>> [cluster-name]-[osd-num] that symlink to ceph-[osd-num]. The ceph-disk >>> command doesn't seem to take a --cluster argument like other commands. >>> >>> Is this a known issue, or am I missing something? >>> _______________________________________________ >>> ceph-users mailing list >>> ceph-users@lists.ceph.com >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >>> >> > _______________________________________________ > ceph-users mailing list > ceph-users@lists.ceph.com > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >
_______________________________________________ ceph-users mailing list ceph-users@lists.ceph.com http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
