Consul is a good fit for this problem, since it lets you register services,
perform consistent lookups when needed, or perform eventually consistent
(faster) lookups via HTTP or DNS. Using consul-template, you can also
reconfigure a reverse proxy like HAProxy or Nginx.
On a related note, I've been wondering how a ZooKeeper/Consul/Etcd tool
fits in with the supervision toolchain, what would be the ideal interface
for such a tool to gel with svscan, ucspi and friends.
On Tue, Mar 8, 2016 at 12:45 PM, <hasse-runit_at_hagenjohansen.dk> wrote:
> Den 08/03/16 kl. 18:50 skrev Buck Evan:
> > What's more, I'm not sure this problem is strictly about ports.
> > I've had situations where a dummy password is generated for a service on
> > startup, and another service must know that dummy password to connect.
> > I believe the general problem is sharing configuration among services.
>
> Maybe a tool for servicediscovery like consul would be helpful. You
> could then stick your configurations options in its builtin key/value
> store?
>
--
Jeremy Voorhis
Received on Tue Mar 08 2016 - 22:46:13 UTC