You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Pete Vander Giessen (JIRA)" <ji...@apache.org> on 2016/07/19 20:46:20 UTC

[jira] [Commented] (BIGTOP-2504) Kafka should be able to bind to something other than 0.0.0.0/the default interface

    [ https://issues.apache.org/jira/browse/BIGTOP-2504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15384825#comment-15384825 ] 

Pete Vander Giessen commented on BIGTOP-2504:
---------------------------------------------

I am currently working on this ticket ...

> Kafka should be able to bind to something other than 0.0.0.0/the default interface
> ----------------------------------------------------------------------------------
>
>                 Key: BIGTOP-2504
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2504
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: deployment
>    Affects Versions: 1.1.0
>            Reporter: Pete Vander Giessen
>            Assignee: Pete Vander Giessen
>            Priority: Minor
>              Labels: juju-charm, kafka
>             Fix For: 1.2.0
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)