Comment 6 for bug 1384341

I dug into this problem a bit more this morning; in the scenario where ceph-public/cluster-address is provided at deployment time (i.e. not changed after deployment), the monitors should all boot from the address they have on the public network; this assumes that the machine the monitor is running on has a IP on the public network - if not it falls back to the private-address (as detail in get_public_addr). If one of the machines does not have an IP on the public network, it will pass 'private-address' to its peers, resulting in a mixed address deployment as described in the original bug report. We should probably switch to a hard configuration choice - if ceph-public-network is provided then no fallback should be used in the event of a mis-configured machine network configuration.

Changing the values of ceph-public-address and ceph-cluster-address post bootstrap of the cluster is current not supported by the charm in any way - i.e. it will make no attempt to reconfigure the daemons running todo the magic trick of re-IPing a running storage cluster. Unfortunately this is not made clear in either the README or the config.yaml, and juju does not have the concept of immutable configuration...