Fix glance standalone when tls-proxy is disabled
We always want to start glance on the internal port now, regardless of whether or not tls-proxy is in use, because we write_local_proxy_http_config() for the standalone case. Change-Id: I47dea645d4a852e02e25af0e1df9c28fec92c42a Co-Authored-By: Radosław Piliszek <radoslaw.piliszek@gmail.com>
This commit is contained in:
parent
eee60c7671
commit
fcbf3e976c
@ -252,6 +252,7 @@ function configure_glance {
|
||||
else
|
||||
write_local_proxy_http_config glance "http://$GLANCE_SERVICE_HOST:$GLANCE_SERVICE_PORT_INT" "/image"
|
||||
iniset $GLANCE_API_CONF DEFAULT bind_host $GLANCE_SERVICE_LISTEN_ADDRESS
|
||||
iniset $GLANCE_API_CONF DEFAULT bind_port $GLANCE_SERVICE_PORT_INT
|
||||
iniset $GLANCE_API_CONF DEFAULT workers "$API_WORKERS"
|
||||
fi
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user