On Tue, Apr 10, 2012 at 16:16, Greg Farnum <gregory.farnum@xxxxxxxxxxxxx> wrote: > Yep, you're absolutely correct. Might as well let users specify the whole address rather than just the port, though — since your patch won't apply to current upstream due to some heartbeating changes I whipped up another one which adds the "osd heartbeat addr" option. It's pushed it to master in commit 6fbac10dc68e67d1c700421f311cf5e26991d39c, but you'll want to backport (easy) or carry your change until you upgrade (and remember to change the config!). :) We're trying to push the "public addr" and "cluster addr" to have a "public network" and "cluster network" alternatives that don't require per-node IP address changes.. Adding more "addr" variants without "network" ones is probably not the most awesome idea. Now, because this is about port allocation, it runs into problems trying to run multiple OSDs per machine without per-osd [osd.42] sections, so I guess that's not as relevant here. I don't have a good suggestion as to what to do for port allocation, apart from ensuring that the port range being used is configurable (or even easily discoverable). -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
