how to force nomad client to bind apps on one network and communicate with nomad server on the other

[David BURET]

Hi,

    My nomad clients have two network interfaces in separate VLAN.

• one  to be used for admin stuff (including nomad client/server communication)
  
• one  to be used by application to bind to it.

How can I setup the nomad client to define that all future jobs should use the 'application card' IP, while using the other one for nomad client/server communication?

I'm lost between all the parameters in the doc... 

thank you.

[Michael Schurter]

We intend on improving the configuration options for our networking, but I believe the existing options should support your use case:

bind_addr controls what IP the Nomad services (HTTP, RPC, Serf) bind to. Set that to your admin IP.

client.network_interface should be set to the interface for applications to bind to.

Consul should advertise the appropriate addresses for both Nomad and applications.

--
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/2d756468-65e1-4e94-9f72-f5c2f5fe4980%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[David BURET]

it works, thanks.

Le lundi 22 mai 2017 19:55:08 UTC+2, Michael Schurter a écrit :

We intend on improving the configuration options for our networking, but I believe the existing options should support your use case:

bind_addr controls what IP the Nomad services (HTTP, RPC, Serf) bind to. Set that to your admin IP.

client.network_interface should be set to the interface for applications to bind to.

Consul should advertise the appropriate addresses for both Nomad and applications.

On Mon, May 22, 2017 at 9:03 AM, David BURET <david...@gmail.com> wrote:

Hi,

    My nomad clients have two network interfaces in separate VLAN.

• one  to be used for admin stuff (including nomad client/server communication)
  
• one  to be used by application to bind to it.

How can I setup the nomad client to define that all future jobs should use the 'application card' IP, while using the other one for nomad client/server communication?

I'm lost between all the parameters in the doc... 

thank you.

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