You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anindya Sinha (JIRA)" <ji...@apache.org> on 2015/10/28 07:32:27 UTC

[jira] [Created] (MESOS-3809) Expose advertise_ip and advertise_port as command line options in mesos slave

Anindya Sinha created MESOS-3809:
------------------------------------

             Summary: Expose advertise_ip and advertise_port as command line options in mesos slave
                 Key: MESOS-3809
                 URL: https://issues.apache.org/jira/browse/MESOS-3809
             Project: Mesos
          Issue Type: Bug
          Components: slave
    Affects Versions: 0.25.0
            Reporter: Anindya Sinha
            Assignee: Anindya Sinha
            Priority: Minor


advertise_ip and advertise_port are exposed as mesos master command line args (MESOS-809). But the following use case makes it a candidate for adding as command line args in mesos slave as well.

On Tue, Oct 27, 2015 at 7:43 PM, Xiaodong Zhang <xd...@alauda.io> wrote:
It works! Thanks a lot.

发件人: haosdent <ha...@gmail.com>
答复: "user@mesos.apache.org" <us...@mesos.apache.org>
日期: 2015年10月28日 星期三 上午10:23
至: user <us...@mesos.apache.org>
主题: Re: How to tell master which ip to connect.

Do you try `export LIBPROCESS_ADVERTISE_IP=xxx` and `LIBPROCESS_ADVERTISE_PORT` when start slave?

On Wed, Oct 28, 2015 at 10:16 AM, Xiaodong Zhang <xd...@alauda.io> wrote:
Hi teams:

My scenarios is like this:

My master nodes were deployed in AWS. My slaves were in AZURE.So they communicate via public ip.
I got trouble when slaves try to register to master. 
Now slaves can get master’s public ip address,and can send register request.But they can only send there private ip to master.(Because they don’t know there public ip,thus they can’t not bind a public ip via —ip  flag), thus  masters can’t connect slaves.How can the slave to tell master which ip master should connect(I can’t find any flags like —advertise_ip in master).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)