You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 24, 2019. It is now read-only.
@foresmac large change here, but one that would be valuable to use on other projects as well. etcd (https://github.com/coreos/etcd) has a very nice Go client that would work well in Vip. Currently all Vip instances are running as naive instances that are unaware of other groupcache peers. Theoretically a Vip instance should be able to come online, ping etcd for other Vip instances, and establish connections to build out the p2p network. This is necessary for Vip clusters to grow organically. The old method of querying for EC2 tags was very hamfisted and worked off and on.
Additionally, any Vip configuration could also live in Etcd (since that's what it's for). That would simplify deployments immensely.
The text was updated successfully, but these errors were encountered:
@foresmac large change here, but one that would be valuable to use on other projects as well. etcd (https://github.com/coreos/etcd) has a very nice Go client that would work well in Vip. Currently all Vip instances are running as naive instances that are unaware of other groupcache peers. Theoretically a Vip instance should be able to come online, ping etcd for other Vip instances, and establish connections to build out the p2p network. This is necessary for Vip clusters to grow organically. The old method of querying for EC2 tags was very hamfisted and worked off and on.
Additionally, any Vip configuration could also live in Etcd (since that's what it's for). That would simplify deployments immensely.
The text was updated successfully, but these errors were encountered: