Yeah we cheat using an ELB instance.
I use fixed ports in my marathon configs and define the listeners in ELB that points to 2 haproxy instances each running marathon-lb. When microservice X is started by Mesos its always reachable by its known port i.e. 31100 which is defined on the ELB that routes to the microservice via marathon-lb generated configs. > On Jan 10 2016, at 10:46 pm, Jeff Schroeder <[email protected]> wrote: On Sunday, January 10, 2016, Rodrick Brown <[rodrick@orchard- app.com](mailto:[email protected])> wrote: > >> We run 100% on AWS and have been running Mesos in production since version 0.19 >> >> Our cluster consists of 3 dedicated zookeeper nodes (M3.2lx), 3 dedicated masters (M3.2lx), 8 dedicated slaves (M4.4xl) and 2 haproxy (M4.Medium) instances used in conjunction with marathon-lb for routing requests into backend services running on Mesos. > > > > Question. You have 2 haproxy nodes also running marathon-lb, or 2 haproxy nodes with 2 more for marathon-lb? Do you use something like keepalived to provide some sort of a vip, or just cheat and use ELB to balance to your haproxy nodes? > > > > Thanks! > >> > > \-- Text by Jeff, typos by iPhone -- *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.
