[ceph-users] octopus cluster deploy with cephadm failed on bootstrap

Hi all, I'm deploying a new octopus cluster using cephadm, follow docs . However it failed on the bootstrap step. According to the logs, key generating failed because of the lack of directory and file. Did I miss something? here is the logs: [

[ceph-users] Re: Cluster network and public network

Hi, I deployed few clusters with two networks as well as only one network. There has little impact between them for my experience. I did a performance test on nautilus cluster with two networks last week. What I found is that the cluster network has low bandwidth usage while public network bandwi

[ceph-users] Re: Cluster network and public network

> Hi, > > I deployed few clusters with two networks as well as only one network. > There has little impact between them for my experience. > > I did a performance test on nautilus cluster with two networks last week. > What I found is that the cluster network has low bandwidth usage During stea

[ceph-users] Re: Cluster network and public network

Hi Anthony, Thanks for the feedback! The servers are using two bond interfaces for two networks. And each interface is bonded with two 25Gb/s cards(active-backup mode). You're right, I should have done the test in a havey recovery or backfill situation. I will benchmark the cluster once again in

[ceph-users] Re: Cluster network and public network

Anthony D'Atri (anthony.datri) writes: > > During heavy recovery or backfill, including healing from failures, > balancing, adding/removing drives, much more will be used. > > Convention wisdom has been to not let that traffic DoS clients, or clients to > DoS heartbeats. [...] > If yo

[ceph-users] Re: Cluster network and public network

>> If your public network is saturated, that actually is a problem, last thing >> you want is to add recovery traffic, or to slow down heartbeats. For most >> people, it isn’t saturated. > >See Frank Schilder's post about a meltdown which he believes could have >been caused by