Your client machine is in 136.172.26.0/24 while your ceph public
network is defined as 10.60.1.0/24. Clients need to be able to reach
the MONs public IP, that's where they get their information from (e.g.
which OSDs they have to talk to). So you'll probably need some routing
to reach the MONs.
Zitat von Amjad Kotobi <kotobi@xxxxxxx>:
On 8. Jun 2020, at 18:01, Eugen Block <eblock@xxxxxx> wrote:
Clients need access to the public network in order to access ceph resources.
What do you mean by access?
E.g. any machines with IP subnet 10.60.1.X/24 able to access CEPH
and perform any operations.
Amjad
Zitat von Amjad Kotobi <kotobi@xxxxxxx>:
Hi,
I’m trying to access CEPH cluster from client machines via RBD for
operations like listing pools, creating image, etc..
I put all needed keys/configuration in ceph directory and when I
try to list pool rbd hung/wait forever
Client machine in IP range of: 136.172.26.0/24
The command e.g. I’m trying is
rbd -c /etc/ceph/ceph.conf -p vms ls -n client.cinder4
My CEPH cluster configuration file “ceph.conf” is
##########
[global]
fsid = e6d92380-4d77-4064-8797-2722fecfd1f4
mon initial members = ceph1,ceph2,ceph3
mon host = 10.60.1.21,10.60.1.22,10.60.1.23
public network = 10.60.1.0/24
auth cluster required = cephx
auth service required = cephx
auth client required = cephx
mon_allow_pool_delete = true
osd pool default size = 3
osd pool default min size = 2
[mgr.ceph1]
mgr tick period = 10
mon mgr beacon grace = 60
[client.cinder4]
keyring = /etc/ceph/ceph.client.cinder4.keyring
##########
There is no firewall in between and accessing/telnet port is very
much possible.
I’m suspecting because of different IP subnet, MON CEPH is not
allowing client.
Any idea and help on this will be great.
Thanks
Amjad
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx