consul

We can embed health checks with consul, so that if a service is unhealthy, it gets pulled out of DNS.

Here are results of running it on consul codebase: $ goimportgraph github.com/hashicorp/consul/...

It would be nice if kubernetes would adopt some of hashicorps stuff like consul, templates, and vault.

Oh and Amazon's head of tax was Luxembourg Honorary Consul to the Seattle are, hum.

But if you're interested there's a lot being done with etcd and consul.

I've never used any of Hashicorps stuff (thought consul did arrive on my radar theother day..).

It would show up in dns as kong.service.consul for other apps to find, so you don't have to hard code IPs in your config.

We use Vagrant for dev and Consul in our deployment and I still have no real idea of what Atlas is.

Instead of setting IPs, you'd connect to this as cassandra.service.consul 2.

This is where tools like consul and mesos-dns come in.

Was hoping that the RFCs gave some ammo for a resolution in my favor, came out more humble and wondering if Consul really needed that many ports.

While I like Consul, and actuallly run Consul in the CoreOS cluster I'm currently building, I have had far fewer problems with Etcd in AWS than Consul.

"When Mesos Met Consul" is a great topic for a talk, because I don't understand why you'd use both.

Consul also is nice because the edges perform the checks (instead of a central server), so the load is distributed.

Atlas is an application that glues together four different projects by Hashicorp: Packer, Vagrant, Terraform and Consul.

Consul, or SkyDNS with something to update Etcd) is viable and often a much easier alternative.