[
https://issues.apache.org/jira/browse/AURORA-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15190237#comment-15190237
]
Kunal Thakar commented on AURORA-1611:
--------------------------------------
Sorry if I wasn't clear. We want to start mesos slaves with
--hostname=<hostname>, which means that the announcer has access to only the
hostname. In this case, in order to announce the IP instead of the hostname, we
can either run an external command (the way I am proposing) or do a DNS
resolution inside the announcer. Running an external command is more flexible,
which is why I prefer that approach.
Another alternative is to change the way AssignedTask is generated
(https://github.com/apache/aurora/blob/master/src/main/java/org/apache/aurora/scheduler/state/TaskAssigner.java#L112)
and insert an IP in that struct, which will then be accessible to the
announcer.
I will add some tests to my proposed change and send it out for review barring
any objections. Thanks!
> 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)
