Consul 0.7

#1

Post by harmw » Thu, Sep 15, 2016, 7:55 AM UTC

Consul 0.7
hashicorp.com

Re: Consul 0.7

#2

Post by dfischer » Thu, Sep 15, 2016, 8:16 AM UTC

Grats Mitch and team!

Re: Consul 0.7

#3

Post by kanwisher » Thu, Sep 15, 2016, 9:33 AM UTC

Have to say consul is one of the most useful tools for service discovery i've ever used. Only feature I want is better support for multiple environments in the same cluster set.

Re: Consul 0.7

#4

Post by bsnape » Thu, Sep 15, 2016, 9:49 AM UTC

A great release with lots of important bug fixes that were giving us issues.

Re: Consul 0.7

#5

Post by heartsucker » Thu, Sep 15, 2016, 10:19 AM UTC

kanwisher wrote: post #3

Have to say consul is one of the most useful tools for service discovery i've ever used. Only feature I want is better support for multiple environments in the same cluster set.

When we used this, we used the first directory to be the env, so it looked like.

    /prod/...
    /stage/...
    /dev/...
    /feature-xyz/...

It's not elegant, but it made for really simple scripts that let us prepend /${env} to every key to access what we needed.

And of course, each service per env had different access tokens so apps in the stage env couldn't read prod keys.

Re: Consul 0.7

#6

Post by discobean » Thu, Sep 15, 2016, 10:49 AM UTC

Thanks for some great tools guys, and a shout out to Fabio another great tool built on top of Consul https://github.com/eBay/fabio

Re: Consul 0.7

#7

Post by lnxusr882 » Thu, Sep 15, 2016, 12:00 PM UTC

Consul combined with consul-template for dynamic config changes in your environment is an extremely powerful solution which just works with minimum fuss.

Works well when deploying clusters such as zookeeper, allows all the nodes to discover each other automatically and work out their id number.

Re: Consul 0.7

#8

Post by dblooman » Thu, Sep 15, 2016, 12:05 PM UTC

lnxusr882 wrote: post #7

Consul combined with consul-template for dynamic config changes in your environment is an extremely powerful solution which just works with minimum fuss. Works well when deploying clusters such as zookeeper, allows all the nodes to discover each other automatically and work out their id number.

Agreed, I wrote a post about this recently, really helps us for small services and there discovery. http://www.dblooman.com/consul/2016/09/11/Consul-and-Service...

Re: Consul 0.7

#9

Post by eis » Thu, Sep 15, 2016, 12:10 PM UTC

Glad to see both etcd and consul support changing multiple keys atomically which I think is a critical feature.

Has someone recently compared the two in production?

Both projects have made some bigger changes in their Raft implementation since the last Jepsen test. I'd love for Kyle to re-do the test and also take into account the transaction feature.

Re: Consul 0.7

#10

Post by zbjornson » Thu, Sep 15, 2016, 2:36 PM UTC

The underlying Serf update was also just released: https://www.hashicorp.com/blog/serf-0.8.html

Awesome company with awesome products.