[jira] [Commented] (AURORA-572) Provide control over listening network interfaces/addresses

["Ivan Vučica (JIRA)" <ji...@apache.org>]

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

Ivan Vučica commented on AURORA-572:
------------------------------------

This seems like it needs some love.

Some workarounds could include running `aurora-scheduler` in a container, or using `iptables` to block external access. But doesn't that seem wrong?

> Provide control over listening network interfaces/addresses
> -----------------------------------------------------------
>
>                 Key: AURORA-572
>                 URL: https://issues.apache.org/jira/browse/AURORA-572
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: T.J. Lipscomb
>            Priority: Minor
>
> Right now, the Aurora scheduler listens on all network interfaces available to the system, but it only chooses one to advertise in zookeeper.
> This is a problem in a situation where a server has two IPs: One external, and one internal (LAN). I can access http://<lan-ip>:<aurora port>/scheduler in my browser, but aurora client commands (and scheduler <-> scheduler interaction) use the external network.
> I want to be able to tell Aurora to communicate on the internal IP (and ideally, not listen on the external one at all, though that can be done at the firewall level), probably through a command line flag.



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