[
https://issues.apache.org/jira/browse/MESOS-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15799560#comment-15799560
]
Stephan Erb commented on MESOS-6281:
------------------------------------
TLDR: Thinking about it, I kind of agree that most of the stuff I worried about
are probably corner cases and we can just use getaddrinfo like you have done in
your tests.
--
Thermos and the user code will end up in the same network namespace. This
implies we have to either make all CNI networks routable to the network of the
Mesos agents, or provide two interfaces - one to access the agent and one for
regular traffic of our service.
Let's suppose we do the latter: We now need a way to find the IP meant for the
service communication so that it can be published in Zookeeper by the executor
(via
https://github.com/twitter/commons/blob/a85b7ad9aae1150190aa8be30b83e5f0bb91508b/src/thrift/com/twitter/thrift/endpoint.thrift#L96).
We must not confuse this with the IP meant for agent communication. Otherwise
external entities might not be able to communicate with our launched
service/app when discovered via Zookeeper
> 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)
