From e00f8426d8e4ed67cf43af039b149dc75abb02d0 Mon Sep 17 00:00:00 2001 From: Diptanu Choudhury Date: Thu, 7 Apr 2016 13:31:32 -0700 Subject: [PATCH] Removing the interfaces block from docs --- website/source/docs/agent/config.html.md | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/website/source/docs/agent/config.html.md b/website/source/docs/agent/config.html.md index 041bf31c8..bd59acec7 100644 --- a/website/source/docs/agent/config.html.md +++ b/website/source/docs/agent/config.html.md @@ -144,22 +144,6 @@ nodes, unless otherwise specified: server nodes from the same datacenter if possible. Used only on server nodes. -* `interfaces`: Provides an alternative to the - `addresses` configuration. Operators can provide network device names to which - Nomad binds individual network services. Nomad looks for the first IPv4 - address configured for the device and uses it, and if no IPv4 address is - present then it looks for an IPv6 address. The value is a map of device names of - network interfaces and supports the following keys: -
- * `http`: The device name the HTTP server is bound to. Applies to both clients and servers. - * `rpc`: The device name to bind the internal RPC interfaces to. Should be exposed - only to other cluster members if possible. Used only on server nodes, but - must be accessible from all agents. - * `serf`: The device name used to bind the gossip layer to. Both a TCP and UDP - listener will be exposed on this address. Should be restricted to only - server nodes from the same datacenter if possible. Used only on server - nodes. - * `advertise`: Controls the advertise address for individual network services. This can be used to advertise a different address to the peers of a server node to support more complex network configurations such as NAT. This