search

universalcore / consular

Receive events from Marathon, update Consul
http://consular.readthedocs.org
BSD 2-Clause "Simplified" License
5 stars 0 forks source link

Containerize Consular #21

Open JayH5 opened 9 years ago

JayH5 commented 9 years ago

Once there are multiple Marathon/Mesos controllers, there should still only be one instance of Consular running.

If we containerize Consular it is easier to run it from Marathon. If it is run from Marathon, when a node falls over, Marathon can move Consular over to a new node and things can carry on running relatively uninterrupted.

JayH5 commented 9 years ago

After speaking to Jeremy, there are potentially different ways to improve availability without running as a container.

The idea of running as a container scheduled by Marathon I got from Mesos-DNS and Kubernetes. They both do something similar with their DNS services (although obviously Kubernetes doesn't use Marathon).