/bigtop

BIGTOP-2504 Kafka should be able to bind to something other than 0.0.0.0/the default interface #134

Closed
wants to merge 4 commits into
from

Conversation

Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@petevg @kwmonroe
@petevg
Contributor

petevg commented Jul 25, 2016

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.

petevg and others added some commits Jul 19, 2016

@petevg
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.
5410483
@petevg
Fixes to puppet recipes.
aeb429f
@petevg
Got rid of default value in cluster.yaml.
a4af988
@kwmonroe
tweak bind_addr default and rendering in server template
a40b83f

@asfgit asfgit closed this in 4747169 Oct 8, 2016

@kwmonroe kwmonroe deleted the juju-solutions:kafka-bind-address-puppet branch Oct 8, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment