Mailing-List: contact user-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@mesos.apache.org
Date: Wed, 02 Dec 2015 12:48:31 -0800 (PST)
References: 
 <CAJQ68qeZj8mw_eP1fkQzq45gbjg_h9kMgvxwaQeid8ep3=wtkw@mail.gmail.com>
In-Reply-To: 
 <CAJQ68qeZj8mw_eP1fkQzq45gbjg_h9kMgvxwaQeid8ep3=wtkw@mail.gmail.com>
User-Agent: NylasMailer/0.4
Message-Id: <1avlswd5lbpl2q0pkj7hboyrb-0@mailer.nylas.com>
Cc: "user@mesos.apache.org" <user@mesos.apache.org>
To: "user@mesos.apache.org" <user@mesos.apache.org>
From: Rodrick Brown <rodrick@orchard-app.com>
Subject: Re: mesos ui best practise - mesos cluster in HA
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="40e2d4367a394e08b1a35d7be33e866d"

--40e2d4367a394e08b1a35d7be33e866d
Content-Type: text/plain; charset=US-ASCII
Mime-Version: 1.0

There's really no use mesos-dns and just point your browser to
http://leader.mesos:5050 to reach the active master.

  
> On Dec 2 2015, at 3:18 pm, Haripriya Ayyalasomayajula
&lt;aharipriya92@gmail.com&gt; wrote:  

>

>  

>

> Hi all,

>

>  

>

> I am having a mesos cluster  (version 0.25.0) running in with 3 masters. I
am getting back to the community regarding the best practise that can be
adopted.

>

>  

>

> -I want to access the UI from a login node. How can I use haproxy in this
case? I have the following HAProxy configuration file on the login node which
has access to the three nodes running masters (servers with ip1, ip2, ip3).

>

>  

>

> #---------------------------------------------------------------------

>

> # Proxy for the mesos-master console

>

> #---------------------------------------------------------------------

>

>  

>

> listen mesos-master [0.0.0.0:5050](http://0.0.0.0:5050)

>

>     mode http  
>

>     option forwardfor

>

>  
>

>         server server1 ip1:5050 check  
>

>         server server2 ip2:5050 check

>

>         server server3 ip3:5050 check

>

> \---

>

> I'd greatly appreciate any inputs here.

>

> Thanks!

>

>  

>

> \--  

>

> Regards,  
Haripriya Ayyalasomayajula

>

>  


-- 
*NOTICE TO RECIPIENTS*: This communication is confidential and intended for 
the use of the addressee only. If you are not an intended recipient of this 
communication, please delete it immediately and notify the sender by return 
email. Unauthorized reading, dissemination, distribution or copying of this 
communication is prohibited. This communication does not constitute an 
offer to sell or a solicitation of an indication of interest to purchase 
any loan, security or any other financial product or instrument, nor is it 
an offer to sell or a solicitation of an indication of interest to purchase 
any products or services to any persons who are prohibited from receiving 
such information under applicable law. The contents of this communication 
may not be accurate or complete and are subject to change without notice. 
As such, Orchard App, Inc. (including its subsidiaries and affiliates, 
"Orchard") makes no representation regarding the accuracy or completeness 
of the information contained herein. The intended recipient is advised to 
consult its own professional advisors, including those specializing in 
legal, tax and accounting matters. Orchard does not provide legal, tax or 
accounting advice.

--40e2d4367a394e08b1a35d7be33e866d
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=US-ASCII
Mime-Version: 1.0

There's really no use mesos-dns&nbsp;and just point your browser to&nbsp;ht=
tp://leader.mesos:5050 to reach the active master.&nbsp;<div><div><br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex;">
  On Dec 2 2015, at 3:18 pm, Haripriya Ayyalasomayajula &lt;aharipriya92@gm=
ail.com&gt; wrote:
  <br>
  <div dir=3D"ltr"><div><br></div><div>Hi all,&nbsp;</div><div><br></div><d=
iv>I am having a mesos cluster &nbsp;(version 0.25.0) running in with 3 mas=
ters. I am getting back to the community regarding the best practise that c=
an be adopted.</div><div><br></div><div>-I want to access the UI from a log=
in node. How can I use haproxy in this case? I have the following HAProxy c=
onfiguration file on the login node which has access to the three nodes run=
ning masters (servers with ip1, ip2, ip3).</div><div><br></div><div>


<p><span>#-----------------------------------------------------------------=
----</span></p>
<p><span># Proxy for the mesos-master console</span></p>
<p><span>#-----------------------------------------------------------------=
----</span></p>
<p><span></span><br></p>
<p><span>listen mesos-master <a href=3D"http://0.0.0.0:5050">0.0.0.0:5050</=
a></span></p>
<p><span>&nbsp; &nbsp; mode http &nbsp;</span></p>
<p><span>&nbsp; &nbsp; option forwardfor</span></p>
<p><span>&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;</span></p>
<p><span>&nbsp; &nbsp; &nbsp; &nbsp; server server1 ip1:5050 check &nbsp;</=
span></p>
<p><span>&nbsp; &nbsp; &nbsp; &nbsp; server server2 ip2:5050 check&nbsp;</s=
pan></p>
<p><span>&nbsp; &nbsp; &nbsp; &nbsp; server server3 ip3:5050 check&nbsp;</s=
pan></p><p><span>---</span></p><p><span>I'd greatly appreciate any inputs h=
ere.</span></p><p><span>Thanks!</span></p></div><div><br></div>-- <br><div>=
<div dir=3D"ltr"><div><div dir=3D"ltr">Regards,<br>Haripriya Ayyalasomayaju=
la&nbsp;<div><br></div></div></div></div></div>
</div>
</blockquote></div>
<br>
<div><font size=3D"1"><font><b>NOTICE TO RECIPIENTS</b>: This communication=
 is confidential and intended for the use of the addressee only. If you are=
 not an intended recipient of this communication, please delete it&nbsp;</f=
ont><font>immediately and notify the sender by return email. Unauthorized r=
eading, dissemination, distribution or copying of this communication is pro=
hibited. This communication does not&nbsp;</font>constitute an offer to sel=
l or a solicitation of an indication of interest to purchase any loan, secu=
rity or any other financial product or instrument, nor is it an offer to se=
ll or a solicitation of an&nbsp;indication of interest to purchase any prod=
ucts or services to any persons who are prohibited from receiving such info=
rmation under applicable law. The contents of this communication may not be=
&nbsp;accurate or complete and are subject to change without notice. As suc=
h, Orchard App, Inc. (including its subsidiaries and affiliates, &quot;Orch=
ard&quot;) makes no representation regarding the&nbsp;<font>accuracy or com=
pleteness of the information contained herein. The intended recipient is ad=
vised to consult its own professional advisors, including those specializin=
g in legal, tax and accounting&nbsp;</font>matters. Orchard does not provid=
e legal, tax or accounting advice.</font></div>
--40e2d4367a394e08b1a35d7be33e866d--