Registrator vs Consul Agent Client

[Madhu Jahagirdar]

We are planning to use Registrator to automatically register services to consul instead of consult client. Should i also use consult client along with registrator ? if so what are the benefits consult client  provides ?

Regards,

Madhu Jahagirdar

[Armon Dadgar]

Hey Madhu,

Registrator performs bridging between the Docker event hub and the Consul agent.

The Consul client is still the one doing all the health checking and registration for the

node, and is required with Registrator.

Hope that helps!

Best Regards,

Armon Dadgar

--
You received this message because you are subscribed to the Google Groups "Consul" group.
To unsubscribe from this group and stop receiving emails from it, send an email to consul-tool...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Madhu Jahagirdar]

If i have 5 docker containers in a host machine, do I need to have consul client in each containers or only one client in the host machine ?

if i need to have one in each containers then i assume i need to use supervisord etc., to run multiple process in a container.

Let me know if my understanding is correct.

Regards,

Madhu Jahagirdar

[Armon Dadgar]

Hey Madhu,

You only need to run a single Consul agent for the entire machine, not per container.

Hope that helps!

Best Regards,

Armon Dadgar

From: Madhu Jahagirdar <madhu.ja...@gmail.com>
Reply: Madhu Jahagirdar <madhu.ja...@gmail.com>>

--

[Madhu Jahagirdar]

I was reading this blog, in which clients are present in each container ? am I reading it incorrectly ? 

Are there use cases where we have to use it per container ?

or 

Because we are using registrator its ok to use it per machine ?

Regards,

Madhu Jahagirdar

 

On Wednesday, 6 May 2015 16:32:58 UTC+5:30, Madhu Jahagirdar wrote:

[Madhu Jahagirdar]

The blog details:

https://hashicorp.com/blog/delta-force-case-study.html

On Wednesday, 6 May 2015 16:32:58 UTC+5:30, Madhu Jahagirdar wrote:

[Subrangshu Sengupta]

Hi Armon,

If I use the REST API of Consul and register services to a Consul agent running as a server on a node, do I still need a consul agent client for that? I guess I can get the health checks from the consul agent server directly as well??

If this is the case, then I can only use a Registrator to registor my services to consul agent server and then I can do away with consul agent client. Please let us know if the agent client provides any other functions which are not provided by Registrator.

Also please correct me if I am wrong.

Regards,

Subrangshu

On Wednesday, May 6, 2015 at 11:11:33 PM UTC+5:30, Armon Dadgar wrote:

Hey Madhu,

Registrator performs bridging between the Docker event hub and the Consul agent.

The Consul client is still the one doing all the health checking and registration for the

node, and is required with Registrator.

Hope that helps!

Best Regards,

Armon Dadgar

[Dana Powers]

does this thread answer your question? https://groups.google.com/forum/#!topic/consul-tool/jdYsvyOWSto

-Dana

[Subrangshu Sengupta]

Hi,

This thread answers my first part of the question as to whether to use HTTP API or agent client. Guess both do pretty much the same work. But I would still like to understand more as to if I use a Registrator as against the consul client.

So the second part of my question, is there anything which consul client provides and is not supported by a Registrator apart from the health checks and DNS querrying?

Regards,

Subrangshu

[Armon Dadgar]

Madhu,

It’s possible to use in both ways. You can run a consul agent in every container,

or just one per host. We recommend one per host, as it reduces the overhead

and is simpler to reason about.

Best Regards,

Armon Dadgar

From: Madhu Jahagirdar <madhu.ja...@gmail.com>
Reply: Madhu Jahagirdar <madhu.ja...@gmail.com>>
Date: May 6, 2015 at 6:39:34 PM
To: consu...@googlegroups.com <consu...@googlegroups.com>>

--

[Armon Dadgar]

Hey Subrangshu,

Every agent (server and client) exposes the same API, so there is no difference between them.

As with registrator, it is just a bridge between Docker and Consul. The Consul functionality is still

powered by the consul agent, and it is required.

Best Regards,

Armon Dadgar

[François Prud'homme]

Hello,

Just for information, a while ago, i have made a test with a consul agent on every containers... and when i was at ~ 40 agents, consul status of each node was flapping... it was only a small vm, but since this test i choose registrator : better to have an event system for each container launch/kill/delete/...

A little question for hashicorp : is it planned to have a tool like registrator maintained by hashicorp ?

It's the only part on my docker infra which is not made by hashicorp ;) Big thanks to all ! Any plan for a enterprise support ?

All the best,

François Prud'homme.

[Armon Dadgar]

Hey,

We do not plan on maintaining registrator ourselves, but we do sponsor GliderLabs to work on it.

Support for all of our tooling is offered through our Atlas product.

Hope that helps!

Best Regards,

Armon Dadgar