On Fri, Dec 19, 2014 at 4:03 PM, Francois Lafont <[email protected]> wrote:
>
> Le 19/12/2014 19:17, Craig Lewis a écrit :
>
> > I'm not using mon addr lines, and my ceph-mon daemons are bound to
> 0.0.0.0:*.
>
> And do you have several IP addresses on your server?
> Can you contact the *same* monitor process with different IP addresses?
> For instance:
> telnet -e ']' ip_addr1 6789
> telnet -e ']' ip_addr2 6789
>
Oh. The second one fails, even though ceph-mon is bound to 0.0.0.0. I
guess that's not going to work.
Looking again... I'm an idiot. I was looking at the wrong column in
netstat. The daemon is bound to a single IP. netstat | grep, with no
column headers bites me again.
I apologize for that wild goose chase.
> Please, could you post your ceph.conf here (or just lines about monitors)?
>
Probably doesn't help now, but:
[global]
fsid = <snip>
mon initial members = ceph0c, ceph1c
mon host = 10.193.0.6:6789, 10.193.0.7:6789
auth client required = none
auth cluster required = none
auth service required = none
cluster network = 10.194.0.0/16
mon warn on legacy crush tunables = false
public network = 10.193.0.0/16
There is something that I don't understand. Personally I
> don't use ceph-deploy and I use manual deployment (because
> I want to make a Puppet deployment of my labs for Ubuntu Trusty
> with Ceph Firefly) and
I'm using Chef, which is also more like a manual deployment than
ceph-deploy.
> when I create my cluster with the
> first monitor, I have to generate a monitor map with this
> command:
>
> monmaptool --create --add {hostname} {ip-address} --fsid {uuid}
> /tmp/monmap
> ^^^^^^^^^^^^
>
> And I have to provide an IP address, so it seems logical to me
> that a monitor is bound to only one IP address.
>
I don't see the Chef rule doing anything like that though.
>
> Can you post your monitors map?
> ceph mon getmap -o /tmp/monmap
> monmaptool --print /tmp/monmap
>
monmaptool: monmap file /tmp/monmap
epoch 2
fsid 1604ec7a-6ceb-42fc-8c68-0a7896c4e120
last_changed 2013-11-22 17:34:21.462685
created 0.000000
0: 10.193.0.6:6789/0 mon.ceph0c
1: 10.193.0.7:6789/0 mon.ceph1c
> > If it's not a traffic volume problem, can you allow the 10.0.2.0/24
> network
> > to route to the 10.0.1.0/24 network, and open the firewall enough? There
> > should be enough info in the network config to get the firewall working:
> > http://docs.ceph.com/docs/next/rados/configuration/network-config-ref/
>
> Yes indeed, It could be enough. But I find it a shame to do this
> workaround because I'm not able to have monitors bound to several
> IP addresses. ;)
>
Looks like you'll have to go this route.
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
