added node ip autodetection

Manager now auto-detects the address that an agent connects to the cluster
from and stores it. This is useful for many kinds of internal cluster
management tools.

Signed-off-by: Drew Erny <drew.erny@docker.com>
Upstream-commit: 9bcf623719104fbd196ab0ca14af48f790980499
Component: engine
This commit is contained in:
Drew Erny
2016-10-24 16:11:25 -07:00
parent 48c9662bdf
commit e11e25579b
6 changed files with 11 additions and 3 deletions

View File

@ -163,6 +163,7 @@ This section lists each version from latest to oldest. Each listing includes a
* Every API response now includes a `Docker-Experimental` header specifying if experimental features are enabled (value can be `true` or `false`).
* The `hostConfig` option now accepts the fields `CpuRealtimePeriod` and `CpuRtRuntime` to allocate cpu runtime to rt tasks when `CONFIG_RT_GROUP_SCHED` is enabled in the kernel.
* The `SecurityOptions` field within the `GET /info` response now includes `userns` if user namespaces are enabled in the daemon.
* `GET /nodes` and `GET /node/(id or name)` now return `Addr` as part of a node's `Status`, which is the address that that node connects to the manager from.
### v1.24 API changes

View File

@ -4464,7 +4464,8 @@ List nodes
}
},
"Status": {
"State": "ready"
"State": "ready",
"Addr": "172.17.0.2"
},
"ManagerStatus": {
"Leader": true,
@ -4555,7 +4556,8 @@ Return low-level information on the node `id`
}
},
"Status": {
"State": "ready"
"State": "ready",
"Addr": "172.17.0.2"
},
"ManagerStatus": {
"Leader": true,