just put a blog post up on running mesos-dns with docker https://mesosphere.com/blog/2015/06/02/get-mesos-dns-up-and-running-in-under-5-minutes-using-docker/ <https://mesosphere.com/blog/2015/06/02/get-mesos-dns-up-and-running-in-under-5-minutes-using-docker/>
and upstart is fine. ken > On Jun 4, 2015, at 4:41 PM, Svante Karlsson <[email protected]> wrote: > > I've just started playing with mesos so excuse me if this is a stupid > question. > > I'm configuring mesos-dns for my very small cluster (initial size) 3 + 3 > nodes. > > I'm planning to use 3 zookeeper nodes combined with mesos masters, chronos, > and marathon and mesos-dns. > > this will be using 3+ nodes as mesos slaves combined with native kafka (not > using mesos) using the same zookeepers. > > I want to use the slave nodes both for kafka and for the service on to on > kafka that performs the actual work. (a massive MQTT broker) > > I looked at the mesos-dns ansible script and realized that is is intended to > run as maraton jobs. > > However I'm inclined to run them on each master node using upstart since I > want to use haproxy to find a "first level proxy" that should live in the > mesos cluster (I think I want fixed addresses to dns for that to work). > > Is there any drawback of that approach (instead of marathon)? > > best regards > svante > > > >
