True :)
On Thu, Apr 2, 2015 at 3:37 PM, Tom Arnfeld t...@duedil.com wrote:
Last time I checked haproxy didn't support UDP which would be key for
mesos-dns.
--
Tom Arnfeld
Developer // DueDil
(+44) 7525940046
25 Christopher Street, London, EC2A 2BS
On Thu, Apr 2, 2015 at 3:53 PM,
We're using a BGP based solution currently to solve the problem of highly
available DNS resolvers.
That might be a route worth taking, and one that could still work via marathon
on top of Mesos.
--
Tom Arnfeld
Developer // DueDil
(+44) 7525940046
25 Christopher Street, London,
You could also just use keepalived for a vip on each mesos-dns instance
assuming they are in the same lan.
On Thursday, April 2, 2015, Tom Arnfeld t...@duedil.com wrote:
We're using a BGP based solution currently to solve the problem of highly
available DNS resolvers.
That might be a route
Fellow Mesos-ers
Firstly, I am loving the speed of Mesos so far. I set up a cluster from
scratch and have been running docker applications with ease with mesos-dns
generating the SRV records. Now I am looking for a serious production setup
on AWS
I see few choices:
1) Start with linux machines,
This is roughly how we've integrated consul dns at client sites. Bind
config still needs updating if/when mesos dns relocates.
--sent from my phone
On Apr 2, 2015 10:30 AM, John Omernik j...@omernik.com wrote:
Based on my earlier emails about the state of service discovery. I did
some
Based on my earlier emails about the state of service discovery. I did
some research and a little writeup on how to use mesos-dns as a forward
lookup zone in a enterprise bind installation. I feel this is more secure,
and more comfortable for an enterprise DNS team as opposed to changing the
I wonder if you registered mesos-dns's port in marathon like you do
docker containers, if you could use the marathon-ha-proxy bridge in
conjunction to allow it to show up anywhere...
On Thu, Apr 2, 2015 at 11:08 AM, James DeFelice
james.defel...@gmail.com wrote:
This is roughly how we've
7 matches
Mail list logo
