search

mantl / mesos-consul

Mesos to Consul bridge for service discovery
Apache License 2.0
338 stars 95 forks source link

Integrate Mesos Into Already Available Consul Environment? #17

Open akamalov opened 9 years ago

akamalov commented 9 years ago

This is a question, not an issue:

Is it Possible to integrate Mesos into already available Consul environment?

stevendborrelli commented 9 years ago

Yes, they function mostly independently of each other. You can probably use some of the roles at https://github.com/CiscoCloud/microservices-infrastructure to register mesos services in consul, and mesos-consul itself just runs in a docker container.

a-nldisr commented 9 years ago

Can you please state the requirements that need to be configured on a running Consul cluster in the documentation.

I have configured a 22 node consul cluster according to the basic consul documentation, added the options based on the playbooks you provided: "bootstrap": "server": "datacenter": "advertise_addr": "data_dir": "ui_dir": "encrypt": "verify_incoming": "verify_outgoing": "ca_file": "cert_file": "key_file": "log_level": "enable_syslog": "start_join": "rejoin_after_leave": But keep getting connection refused on interfaces that run no firewall. I turned off a client on one of the nodes, configured the mesos-consul to use the ssl certificates that the cluster is using and keep getting this error but cannot locate why it refuses to register. More documentation is greatly appreciated.

Update: Found out that each consul node was binding port 8600 to localhost and it was required to put -client=0.0.0.0 (or for more secure option to place a private ip in it, but this breaks all commands such as consul members etc) to be able to have mesos-consul connect to the existing cluster.