[jira] [Commented] (MESOS-6281) Document how executors can obtain the IP address of the container

["Avinash Sridharan (JIRA)" <ji...@apache.org>]

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

Avinash Sridharan commented on MESOS-6281:
------------------------------------------

[~StephanErb] if its a question of discovering all the non-local IP address assigned to that network namespace why can't you rely on system calls to discover all the IP addresses. Here is an example of how we do it in the `libprocess` world:
https://github.com/apache/mesos/blob/master/src/tests/containerizer/cni_isolator_tests.cpp#L66-L76


Also, just curious to know, if you know all the IP addresses allocated to the network namespace and announce to ZK, how would frameworks like AURORA figure out which IP address to use?

> 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)