Nomad + Consul + Weave / overlay networks

[Samuel Berthe]

Hi guys,

I’m trying to build a container cluster with Consul and Nomad. For the networking layer, I’m testing an overlay network with Weave:

client {

    enabled = true

    options {

        "docker.endpoint" = "unix:///var/run/weave/weave.sock"

    }

}

Unfortunately, I didn’t find in the doc neither in the code how to sync consul with the IP of the container ethwe network interface. Did I miss anything ?

How do you basically setup overlay network ?

Rgds

[Diptanu Choudhury]

Hi Samuel,

Nomad client doesn't currently understand overlay networks and hence if you are using weave to assign a container some IP, nomad won't have knowledge about that so it won't register that IP with Consul.

Currently, Nomad only supports registering the host IP with Consul. Network plugins are on the roadmap, they will enable such use cases. 

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/nomad/issues
IRC: #nomad-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Nomad" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nomad-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nomad-tool/0a60f10b-ca23-459a-a7ec-5a023035c0ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks,
Diptanu Choudhury

Web - www.linkedin.com/in/diptanu

Twitter - @diptanu

[Samuel Berthe]

Do you know the ETA for that feature ? 0.6 ? later ?

How do you basically manage networking / dns / ports in a platform based on consul and nomad ?

I mean, if you setup a task with a redis instance, deployed on 3 nodes, ports will be different for each single redis container. Then using DNS (pointing on a random node) is not possible. Do you run services in consul-template, setting env variables to fixed ip and port ?

I'm scared about running each single container from a consul-template process: because reloading redis == reloading redis dependences == reloading dependences of redis dependencies...

WDYT ?

Rgds

On Friday, September 30, 2016 at 7:03:48 PM UTC+2, Diptanu Choudhury wrote:

Hi Samuel,

Nomad client doesn't currently understand overlay networks and hence if you are using weave to assign a container some IP, nomad won't have knowledge about that so it won't register that IP with Consul.

Currently, Nomad only supports registering the host IP with Consul. Network plugins are on the roadmap, they will enable such use cases. 

On Fri, Sep 30, 2016 at 5:38 AM, Samuel Berthe <con...@samuel-berthe.fr> wrote:

Hi guys,

I’m trying to build a container cluster with Consul and Nomad. For the networking layer, I’m testing an overlay network with Weave:

client {

    enabled = true

    options {

        "docker.endpoint" = "unix:///var/run/weave/weave.sock"

    }

}

Unfortunately, I didn’t find in the doc neither in the code how to sync consul with the IP of the container ethwe network interface. Did I miss anything ?

How do you basically setup overlay network ?

Rgds

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/nomad/issues
IRC: #nomad-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Nomad" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nomad-tool+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/nomad-tool/0a60f10b-ca23-459a-a7ec-5a023035c0ad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alex Dadgar]

Hey Samuel,

SDN is on the roadmap! As for now, your options are consul-template which is getting first class integration in the coming release, or to use static ports for the redis and just use Consul based DNS. As for now, if you wanted to do an overlay network you would have to use raw_exec driver and set it up yourself.

Thanks,

Alex

To unsubscribe from this group and stop receiving emails from it, send an email to nomad-tool+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nomad-tool/3974f62c-48ad-438d-9c79-995995a040cc%40googlegroups.com.