Ceph Monitor Charm

  1. Bug #1384341
  2. Comment #5

Comment 5 for bug 1384341

Revision history for this message
Florian Haas (fghaas) wrote : Re: when enable ceph-public-network and ceph-cluster-network, ceph-mon cannot communicate each other

Looking into this a little more closely, it appears that the charm does attempt to do the right thing in http://bazaar.launchpad.net/~openstack-charmers/charms/trusty/ceph/trunk/view/head:/hooks/utils.py#L74. However, this only fires on mon-relation-changed, so the only way to get this updated is to remove a unit and then redeploy it.

Even so, the charm makes no attempt to update the monmap, so while peers are instructed to find the mons at the new address, the mon doesn't actually start to *listen* on that address, as it will select its listening IP based not on ceph.conf, but on the monmap.

See also: http://docs.ceph.com/docs/master/rados/operations/add-or-rm-mons/#changing-a-monitor-s-ip-address

That means that if you change ceph-public-network in an existing deployment, and you redeploy all units, what you'll end up with is a "mon hosts" entry in all your hosts' ceph.conf that does not contain a single IP that a mon is actually listening on.