Hi Steven, I've just been playing around with mesos-consul.
Am I correct in thinking that the service requires a consul client to be running on every host in the mesos cluster? Is there any way to get it to run so that it communicates with a central consul cluster rather than having to run the client on every host? Thanks, Aaron ________________________________________ From: Steven Borrelli [[email protected]] Sent: 30 April 2015 01:40 To: [email protected]; [email protected] Cc: Keith Chambers (kechambe); Chris Aubuchon Subject: Announcing: Mesos Consul service discovery bridge 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.
