Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Containerize Consular #21

Open
JayH5 opened this issue Aug 17, 2015 · 1 comment
Open

Containerize Consular #21

JayH5 opened this issue Aug 17, 2015 · 1 comment

Comments

@JayH5
Copy link
Contributor

JayH5 commented Aug 17, 2015

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
Copy link
Contributor Author

JayH5 commented Aug 19, 2015

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).

This was referenced Feb 18, 2016
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JayH5