Thanks, yeah we will move away from it. Sadly, this is one of many
little- (or non-) documented things that have made adapting Ceph for
large-scale use a pain. Hopefully it will be worth it.
On Mon, Apr 23, 2018 at 4:25 PM, David Turner wrote:
> If you can move away from having a non-default
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.con
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 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 li
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
wrote:
>
> If I use another cluster name (other than th
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 iss
