ceph will always bind to the local IP. It can't bind to an IP that isn't assigned directly to the server such as a NAT'd IP. So your public network should be the local network that's configured on each server. If you cluster network is 10.128.0.0/16 for instance your public network might be 10.129.0.0/16.
The public bind addr allows you to specify a NAT'd IP for each of your monitors. You monitors will then advertise this IP address so that your clients know to reach them at their NAT'd IP's rather than their local IP's. This does NOT apply for OSD IP's. Your clients must be able to route to the OSD's directly. If your OSD servers are behind a NAT I don't think that configuration is possible nor do I think it would be a good idea to route your storage traffic through a NAT.
_______________________________________________ ceph-users mailing list [email protected] http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
