This is one of three pull requests for setting up the ability to bind kafka to an interface/ip address. I've run bundletester with the following permutations of 'bind_addr' in config.yaml:
1) Keeping the default value of null doesn't break anything, which is expected.
2) Passing in a value of 0.0.0.0 doesn't break anything, which is expected.
3) Passing in an address that doesn't match the address of the kafka server (e.g., 10.0.9.9) does break things.
My juju fu is not strong enough to setup a second interface on a machine and bind to that, but the above three tests do seem to indicate that the code does what I think that it does.
As part of this work, I also fixed up the kafka tests. It should be easy to get them to run, even if you aren't paying attention to anything other than having the right branch of layer-apache-bigtop-base checked out locally. (The branch is 'kafka-bind-address', incidentally)
@juju-solutions/bigdata
This is one of three pull requests for setting up the ability to bind kafka to an interface/ip address. I've run bundletester with the following permutations of 'bind_addr' in config.yaml:
1) Keeping the default value of null doesn't break anything, which is expected. 2) Passing in a value of 0.0.0.0 doesn't break anything, which is expected. 3) Passing in an address that doesn't match the address of the kafka server (e.g., 10.0.9.9) does break things.
My juju fu is not strong enough to setup a second interface on a machine and bind to that, but the above three tests do seem to indicate that the code does what I think that it does.
As part of this work, I also fixed up the kafka tests. It should be easy to get them to run, even if you aren't paying attention to anything other than having the right branch of layer-apache-bigtop-base checked out locally. (The branch is 'kafka-bind-address', incidentally)