Sounds great!
>libprocess should always bind to 0.0.0.0
Do you proposal include this?
On Mon, Oct 17, 2016 at 2:12 AM, Jie Yu wrote:
> OK, guys. Thanks for the input! Here is my proposal:
>
> 1) If the container uses host network, Mesos agent will set
>
OK, guys. Thanks for the input! Here is my proposal:
1) If the container uses host network, Mesos agent will set
LIBPROCESS_ADVERTISE_IP
to agent IP. This is for the case where DNS is not configured properly on
the host (we don't need to do that if DNS is configured properly). By doing
this,
good point, +1
2016-10-13 0:27 GMT+08:00 Jie Yu :
> Stephan,
>
> I think the only time the framework needs to set LIBPROCESS_ADVERTISE_IP is
> when DNAT is necessary for the container (e.g., bridge). In that
> case, LIBPROCESS_ADVERTISE_IP should always be agent ip and
> the
Stephan,
I think the only time the framework needs to set LIBPROCESS_ADVERTISE_IP is
when DNAT is necessary for the container (e.g., bridge). In that
case, LIBPROCESS_ADVERTISE_IP should always be agent ip and
the relevant host port allocated for the container. For other cases,
framework should
>
> Also, I think libprocess should always bind to 0.0.0.0, rather than doing a
> hostname lookup and bind to the IP found for the hostname.
> LIBPROCESS_ADVERTISE_IP can be used to overwrite the ip address it wants to
> advertise to peers. If that's not specified, it'll try to do a hostname
>
>Framework should be the one that sets
>LIBPROCESS_ADVERTISE_IP and LIBPROCESS_ADVERTISE_PORT appropriately if it
>tries to launch another Mesos framework so that Master can reach the new
>framework.
As a framework/executor author this is not possible in all scenarios: There is
no way to
>
> While I believe this particular logic of setting LIBPROCESS_ADVERTISE_IP
> to agent IP can be done in the agent (it could look at the port mapping
> as well)
What if there are multiple port mappings? How can the agent decide which
port to be used as LIBPROCESS_ADVERTISE_PORT?
On Tue, Oct