Hi Eugen,
The issue looks fixed now in my kernel client mount works fine without
cluster IP.
I have re-run "ceph config set osd cluster_network 10.100.4.0/24" and
restarted all service. Eearlier it was run with "ceph config set global
cluster_network 10.100.4.0/24".
I have run the command output
Do you find any issue in the below commands I have used to set cluster IP
in cluster.
Yes I do:
### adding public IP for ceph cluster ###
ceph config set global cluster_network 10.100.4.0/24
I'm still not convinced that your setup is as you want it to be.
Can you share your actual config?
c
Hi Eugen,
I have only added my Public IP and relevant hostname to hosts file.
Do you find any issue in the below commands I have used to set cluster IP
in cluster.
### adding public IP for ceph cluster ###
ceph config set global cluster_network 10.100.4.0/24
ceph orch daemon reconfig mon.host1
Hi Janne,
My OSD's have both public IP and Cluster IP configured. The monitor node
and OSD nodes are co-located.
regards
Amudhan P
On Tue, Nov 10, 2020 at 4:45 PM Janne Johansson wrote:
>
>
> Den tis 10 nov. 2020 kl 11:13 skrev Amudhan P :
>
>> Hi Nathan,
>>
>> Kernel client should be using on
Could it be possible that you have some misconfiguration in the name
resolution and IP mapping? I've never heard or experienced that a
client requires a cluster address, that would make the whole concept
of separate networks obsolete which is hard to believe, to be honest.
I would recommend
Den tis 10 nov. 2020 kl 11:13 skrev Amudhan P :
> Hi Nathan,
>
> Kernel client should be using only the public IP of the cluster to
> communicate with OSD's.
>
"ip of the cluster" is a bit weird way to state it.
A mounting client needs only to talk to ips in the public range yes, but
OSDs always
Hi Nathan,
Kernel client should be using only the public IP of the cluster to
communicate with OSD's.
But here it requires both IP's for mount to work properly.
regards
Amudhan
On Mon, Nov 9, 2020 at 9:51 PM Nathan Fish wrote:
> It sounds like your client is able to reach the mon but not th
Hi Eugen,
Yes, you're right other than OSD's rest don't require cluster IP.
But in my case, I don't know what went wrong my kernel client requires
cluster IP for the mount to work properly.
About my setup; :-
Cluster Initially bootstrapped configured with public IP only, later added
cluster IP b
It sounds like your client is able to reach the mon but not the OSD?
It needs to be able to reach all mons and all OSDs.
On Sun, Nov 8, 2020 at 4:29 AM Amudhan P wrote:
>
> Hi,
>
> I have mounted my cephfs (ceph octopus) thru kernel client in Debian.
> I get following error in "dmesg" when I try
Clients don't need the cluster IP because that's only for OSD <--> OSD
replication, no client traffic. But of course to be able to
communicate with Ceph the clients need a public IP, how else would
they contact the MON? Or did I misunderstand your setup?
Zitat von Amudhan P :
Hi,
I have
10 matches
Mail list logo
