[
https://issues.apache.org/jira/browse/MESOS-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781376#comment-15781376
]
Zameer Manji commented on MESOS-6281:
-------------------------------------
It is possible to use system calls. It is the second option listed in the
ticket.
This ticket is about documenting what the best practice is and what options can
be used by executors regardless of isolation. The chat in #containerizer
references some confusion on what an executor should do. IMHO, {{NetworkInfo}}
should be exposed to the executor, it is the simplest method and it should work
in all isolation cases.
In Aurora's case the framework doesn't consume the IP addresses for any reason,
the executor is simply publishing the IP address to ZK for discovery. Here we
are trying to determine the public IP address(es) of the task to advertise so
it can be discovered.
> 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)
