[
https://issues.apache.org/jira/browse/MESOS-3809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080520#comment-15080520
]
Anindya Sinha commented on MESOS-3809:
--------------------------------------
Thanks [~metskem]. Looks like that this commit did not actually make it into
0.26. It does show up in the file "CHANGELOG" in the tag "0.26.0" (as well as
the tag "0.26.0-rc2" when it was first introduced), but the actual commit did
not make it. I will follow up and update accordingly.
For the tag 0.26:
https://github.com/apache/mesos/blob/0.26.0/CHANGELOG#L58: This adds MESOS-3809
into this release (as in CHANGELOG).
But the change in docs/configuration.md
(https://github.com/apache/mesos/blob/0.26.0/docs/configuration.md) and
src/slave/main.cpp
(https://github.com/apache/mesos/blob/0.26.0/src/slave/main.cpp) is missing
based on original commit in master which is:
bb5c44a7a6fead84789c933a9aa3e1a8cf35722d Added 2 slave flags --advertise_ip and
--advertise_port.
> 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
> Labels: mesosphere
> Fix For: 0.26.0
>
>
> 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 <xdzh...@alauda.io> wrote:
> It works! Thanks a lot.
> 发件人: haosdent <haosd...@gmail.com>
> 答复: "u...@mesos.apache.org" <u...@mesos.apache.org>
> 日期: 2015年10月28日 星期三 上午10:23
> 至: user <u...@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 <xdzh...@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)
