[
https://issues.apache.org/jira/browse/AURORA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186044#comment-15186044
]
Kunal Thakar commented on AURORA-1611:
--------------------------------------
It won't. We are not planning to deploy aurora client on all engineer laptops,
which is the location of the problem. Also, as I mentioned above, we are
planning to run other frameworks in the mesos cluster.
Additionally, this sort of approach will also be required to support the
IP-per-container world
(https://mesosphere.com/blog/2015/12/02/ip-per-container-mesos/), which is not
very far in the future.
> Add support for IP addresses instead of just hostnames in Announcer
> -------------------------------------------------------------------
>
> Key: AURORA-1611
> URL: https://issues.apache.org/jira/browse/AURORA-1611
> Project: Aurora
> Issue Type: Story
> Reporter: Kunal Thakar
>
> The thermos announcer is passing hostnames in the serviceEndpoint object that
> is sent to ZK. We want the announcer to send IPs instead or in addition to
> the hostname that is passed along. What is the best way to achieve this? I am
> thinking of adding a new attribute to the Endpoint struct
> (https://github.com/apache/aurora/blob/master/commons/src/main/thrift/org/apache/aurora/common/thrift/endpoint.thrift).
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
