[
https://issues.apache.org/jira/browse/AURORA-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218682#comment-14218682
]
Stephan Erb commented on AURORA-572:
------------------------------------
Probably the interface should look similar to what Mesos offers: --ip and
--hostname so both can be controlled independently. This addition would not
only be needed for Aurora but also for Thermos.
In my specific case, all hosts have a management interface and a service
interface. Aurora and Mesos should only use the latter. Unfortunately Aurora is
currently announcing (and redirecting to) the internal unroutable hostname
instead of the ip-address of the service interface.
> 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)
