Mailing-List: contact user-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@mesos.apache.org
MIME-Version: 1.0
In-Reply-To: <d1a7a098-926a-9720-f7cf-e7913b12ee46@illinois.edu>
References: <d1a7a098-926a-9720-f7cf-e7913b12ee46@illinois.edu>
Date: Thu, 26 May 2016 00:45:58 +0800
Message-ID: <CAFt=ROMz_StsQe4XjZj=i96DFLwyNCAUgiB36mZNuWnih1C_=Q@mail.gmail.com>
Subject: Re: Mesos and Openstack
From: haosdent <haosdent@gmail.com>
To: user <user@mesos.apache.org>
Content-Type: multipart/alternative; boundary=001a113dde1675f5d30533ad68d1
archived-at: Wed, 25 May 2016 16:46:03 -0000

--001a113dde1675f5d30533ad68d1
Content-Type: text/plain; charset=UTF-8

>If I use the slaves internal IP address like 192.168.1.40 it can make the
connection with Mesos master, but then dies and keeps reconnecting.
Does the network from Master to Slave and from Slave to Master work fine if
you use internal IP? And may you show the log related to "dies and keeps
reconnecting"?

On Wed, May 25, 2016 at 11:16 PM, Omar Sobh <omarsobh@illinois.edu> wrote:

> Hello all,
>
> I have a number of mesos slave inside and openstack installation that i'm
> trying to connect to a master on a different subnet. If I use the slaves
> internal IP address like 192.168.1.40 it can make the connection with Mesos
> master, but then dies and keeps reconnecting. If I map it to the public
> interface it dies from spawning too fast. The public IP address isn't
> visible inside the host but i've mapped it via openstack floating IP
> addresses so I know the VM is getting it. Are there any ideas on how I can
> connect these VM's to the Mesos master, and why do they die out with
> internal IP's and a public interface mapping?
>
>
> best,
>
> O
>
>


-- 
Best Regards,
Haosdent Huang

--001a113dde1675f5d30533ad68d1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt;<span style=3D"font-size:12.8px">If I use the slaves i=
nternal IP address like 192.168.1.40 it can make the connection with Mesos =
master, but then dies and keeps reconnecting.</span><div><span style=3D"fon=
t-size:12.8px">Does the network from Master to Slave and from Slave to Mast=
er work fine if you use internal IP? And may you show the log related to &q=
uot;</span><span style=3D"font-size:12.8px">dies and keeps reconnecting</sp=
an><span style=3D"font-size:12.8px">&quot;? =C2=A0</span></div></div><div c=
lass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, May 25, 2016 at=
 11:16 PM, Omar Sobh <span dir=3D"ltr">&lt;<a href=3D"mailto:omarsobh@illin=
ois.edu" target=3D"_blank">omarsobh@illinois.edu</a>&gt;</span> wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">Hello all,<br>
<br>
I have a number of mesos slave inside and openstack installation that i&#39=
;m trying to connect to a master on a different subnet. If I use the slaves=
 internal IP address like 192.168.1.40 it can make the connection with Meso=
s master, but then dies and keeps reconnecting. If I map it to the public i=
nterface it dies from spawning too fast. The public IP address isn&#39;t vi=
sible inside the host but i&#39;ve mapped it via openstack floating IP addr=
esses so I know the VM is getting it. Are there any ideas on how I can conn=
ect these VM&#39;s to the Mesos master, and why do they die out with intern=
al IP&#39;s and a public interface mapping?<br>
<br>
<br>
best,<br>
<br>
O<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature">Best Regards,<br><div>Haosdent Huang</div></div>
</div>

--001a113dde1675f5d30533ad68d1--