-
Notifications
You must be signed in to change notification settings - Fork 33
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.
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
Documents on deployment with consul? #291
Comments
I finally set up consul server on the master and consul agent on the Mesos-node. However, I cannot register task to consul... My marathon app JSON:
And marathon-consul log:
|
I read the code and found only healthy services are registered... |
I encounter problem again... How can I use marathon-consul as DNS?
But I cannot dig the FQDN:
Maybe I need a Mesos-DNS in addition to marathon-consul? |
As long as I enabled DNS in the Consul agent configuration file, all registered services were available via DNS unless they have characters in the name that are not allowed in domain names. The marathon-consul logs will tell you if a service can't be registered with Consul DNS. Does the consul service resolve in DNS for you? That should be registered by default.
|
I am not familiar with consul. I thought I need to run a consul server along with marathon-consul in Mesos-master. And run consul-agent in each Mesos-agent ?
I am a bit confused on the relationship between marathon-consul and consul-server, because there is no config about consul-server address...
The text was updated successfully, but these errors were encountered: