In Multi host deployments, it is possible to run ETCD in a different
host than the SERVICE_HOST (where all the controllers run). This patch
brings that distinction.
Change-Id: I15fe6f25eedf1efebaab81cce26b080577b856cc
Signed-off-by: Antoni Segura Puimedon <antonisp@celebdor.com>
| ... | ... |
@@ -53,9 +53,9 @@ function start_etcd3 {
|
| 53 | 53 |
cmd+=" --initial-cluster-state new --initial-cluster-token etcd-cluster-01" |
| 54 | 54 |
cmd+=" --initial-cluster $HOSTNAME=http://$SERVICE_HOST:2380" |
| 55 | 55 |
cmd+=" --initial-advertise-peer-urls http://$SERVICE_HOST:2380" |
| 56 |
- cmd+=" --advertise-client-urls http://$SERVICE_HOST:$ETCD_PORT" |
|
| 56 |
+ cmd+=" --advertise-client-urls http://${HOST_IP}:$ETCD_PORT"
|
|
| 57 | 57 |
cmd+=" --listen-peer-urls http://0.0.0.0:2380 " |
| 58 |
- cmd+=" --listen-client-urls http://$SERVICE_HOST:$ETCD_PORT" |
|
| 58 |
+ cmd+=" --listen-client-urls http://${HOST_IP}:$ETCD_PORT"
|
|
| 59 | 59 |
|
| 60 | 60 |
local unitfile="$SYSTEMD_DIR/$ETCD_SYSTEMD_SERVICE" |
| 61 | 61 |
write_user_unit_file $ETCD_SYSTEMD_SERVICE "$cmd" "" "root" |