GitHub user petevg opened a pull request:
https://github.com/apache/bigtop/pull/134
BIGTOP-2504 Kafka should be able to bind to something other than
0.0.0.0/the default interface
For security reasons, some people deploying kafka would like to bind it to
listen on a specific network interface. Details in this ticket, filed against
the kafka juju charm:
https://bugs.launchpad.net/charms/+source/apache-kafka/+bug/1602666
This ticket tracks work to add the necessary hooks in the puppet scripts.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/juju-solutions/bigtop
kafka-bind-address-puppet
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/bigtop/pull/134.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #134
----
commit 54104839c91e6fed9281967a8629d3f9ea27d68c
Author: Pete Vander Giessen <[email protected]>
Date: 2016-07-19T20:40:35Z
Added bind_addr value for server.properties
If set to something that ruby evaluates as true, will be written to
server.properties. Causes the server to listen on the ip/interface
indicated by the value of the string.
commit aeb429fa5c541835d6f3507867329cc470239b8c
Author: Pete Vander Giessen <[email protected]>
Date: 2016-07-21T17:33:55Z
Fixes to puppet recipes.
commit a4af9887494ee44ad7fd061a8262d62b1d8d517b
Author: Pete Vander Giessen <[email protected]>
Date: 2016-07-22T14:32:19Z
Got rid of default value in cluster.yaml.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
