proposal: binding address and advertise address about dragonboat

[lni]

there are cases we cannot use the RaftAddress as the binding address such as in docker

I think what you are trying to suggest is that when using the Master server component, which is optional, the RaftAddress can't be used as the binding address where there is private/public address mapping. e.g. a nodehost binds to the private address 10.0.0.1:80 when it is accessible by a remote program from a public address say node1.mydomain.com:8080.

This has nothing to do with docker as you can have similar setup in other environment while docker users may choose to use the host network driver to avoid such mapping.

For most users, when they are not using the optional Master server, there is actually nothing for a NodeHost to advertise. The above mapping is managed by user programs - RaftAddress can be set to the private address so the NodeHost listens on it. All Raft member addresses (specified when you start cluster or do membership changes) should be using the public addresses. With the correct docker published port configuration, such setup should work fine in docker.

Is there any chance to add an advetise address?

I agree that when using the optional Master server component, the address used to identify the NodeHost should be the public address and it should be explicitly separated from the bind address.

Considering to add a bind address to the config and keep RaftAddress as the identification.

[gensmusic]

great, also, in my case, docker using host network is not allowed by some security policy in my company.

[lni]

I've edited the original post to better describe the issue.

[lni]

@gensmusic this issue has been resolved in 968d735

please note that the Master server support will be reworked in the major release, details in #32.

[gensmusic]

cool

[lni]

@gensmusic please try the version in the Master branch and let me know if you see anything strange. thanks!