WIP: Add support for etcd registry. #53
Conversation
This is initial support for the etcd service to be used as a registry.
|
Nice! This sounds very interesting |
uses uris to configure etcd servers
This is initial support for the etcd service to be used as a registry.
Conflicts: Gemfile lib/dcell/registries/etcd_adapter.rb spec/dcell/registries/etcd_adapter_spec.rb
|
looks pretty cool! |
|
I don't know if this is still an important dev here as one of the idea is to implement own, DCell-based KVS. This won't only allow to get rid of the dependency, but the whole system will gain a control and synchronization framework(to support self healing or automatic cluster growth or shrinking). The key-value storage will be just a "side effect". |
|
@niamster perhaps you're thinking of something like this? |
|
https://github.com/zeromq/zyre now has official ruby bindings, but current master doesn't compile. I will try to get a PR ready for it so it compiles again and come up with some examples. What it basically does is to manage a group of peers as they join and leave a group and/or a network, it can also handle timeouts. |
|
@tarcieri I was in fact thinking about introducing Raft as part of DCell to control the nodes(monitoring, spawning/shutting down containers that host nodes, the node may itself go offline if it doesn't receive enough attention and there's enough nodes to serve). |
|
@Asmod4n zyre is interesting only for a cluster within a single network but it's useless with containers that are located in different clusters. Please correct me if I'm wrong |
|
@niamster zyre by default uses udp beaconing, but you can configure it to use a gossip protocol over tcp. Have written a little bit about how it works here: #89 (comment) |
|
@Asmod4n I'm not sure that malamute can fit here as author's targeting it as streaming engine. |
Work in progress. Please do not merge!
This is initial support for the etcd service to be used as a registry.