[
https://issues.apache.org/jira/browse/MESOS-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15565487#comment-15565487
]
Stephan Erb commented on MESOS-6281:
------------------------------------
>From the perspective of an executor author, I would prefer if the multiple
>IP-addresses attached to the network namespace of the executor are made
>readily available in a protobuf. This implies that no custom and potentially
>flaky code relying on a combination of {{LIBPROCESS_IP}} or {{getaddrinfo}} is
>required.
Therefore the question: Would it be possible to move or duplicate this
[Slave::_statusUpdate
code|https://github.com/apache/mesos/blob/1fe48d388af378176be02b814bb3c7109b90a40d/src/slave/slave.cpp#L3820-L3824]
also to (for example)
[ExecutorProcess.runTask|https://github.com/apache/mesos/blob/master/src/exec/exec.cpp#L331]?
Or would this violate assumptions or standards that TaskInfo is only ever
modified by the framework submitting the task?
/cc [~anandmazumdar] [~zhitao]
> Document how executors can obtain the IP address of the container
> -----------------------------------------------------------------
>
> Key: MESOS-6281
> URL: https://issues.apache.org/jira/browse/MESOS-6281
> Project: Mesos
> Issue Type: Improvement
> Reporter: Zameer Manji
> Assignee: Avinash Sridharan
> Priority: Minor
>
> From the discussion in #containerizer on Slack.
> Documentation would be nice on the best practice on how an executor can
> obtain the IP address of the container. Some options were discussed:
> * Should it check {{LIBPROCESS_IP}}?
> * Should it use {{getaddrinfo(3)}}?
> * Should {{NetworkInfo}} be exposed to the executor?
> A concrete use case of this would be for thermos (Aurora's executor). It
> needs to figure out an ip address to announce to ZK for discovery.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
