Can you help describe the differences between this project and something like mesos-dns?
On Wed, Apr 29, 2015 at 7:40 PM, Steven Borrelli <[email protected]> wrote: > I’m pleased to announce the open-source release of a mesos-consul bridge > at https://github.com/CiscoCloud/mesos-consul. > > Mesos-consul automatically registers/deregisters Mesos tasks into Consul’s > service catalog, so that task information available for discovery via > Consul’s DNS service or API. > > This means if you have a Mesos application called “application", this > program will register the application in Consul. The servers where the > application is running can be located via DNS as > “application.service.consul”, with the port being exposed via DNS SRV. > > This program also does Mesos leader discovery, so that > leader.mesos.service.consul will point to the current leader. > > The project includes a Dockerfile to build in a single step, and > instructions on how to run the container in Marathon. > > Special thanks to Cisco Cloud for sponsoring this project and Chris > Aubuchon, the primary engineer on the project. > > > >
