-
Notifications
You must be signed in to change notification settings - Fork 15
Description
tendrl-ansible uses two variables related to the configuration of etcd with following description[1]:
etcd_ip_address
configures where etcd instance is listening,etcd_fqdn
configure tendrl components to be able to connect to etcd instance
The first parameter - etcd_ip_address
- is used to configure following two etcd configuration variables: ETCD_LISTEN_CLIENT_URLS
and ETCD_ADVERTISE_CLIENT_URLS
.
The second parameter - etcd_fqdn
- is not directly used in etcd configuration, but it is used to configure etcd clients - where to connect to the etcd server.
The problem is, that ETCD_LISTEN_CLIENT_URLS
might be configured with 0.0.0.0
, which means, that etcd will listen on all interfaces[2].
But this value doesn't make sense for the ETCD_ADVERTISE_CLIENT_URLS
- where should be valid IP or fqdn[3].
From my point of view, it will make sense to use the value from etcd_fqdn
for ETCD_ADVERTISE_CLIENT_URLS
.
So the configuration values will be used this way:
etcd_ip_address
=>ETCD_LISTEN_CLIENT_URLS
(as it is now)etcd_fqdn
=>ETCD_ADVERTISE_CLIENT_URLS
(proposed change)
[1] https://github.com/Tendrl/tendrl-ansible/blob/master/README.md
[2] https://coreos.com/etcd/docs/latest/op-guide/configuration.html#listen-client-urls
[3] https://coreos.com/etcd/docs/latest/op-guide/configuration.html#advertise-client-urls