Fix service start sequence
1. zmq-receiver should be started in advance 2. when using zeromq driver, nova-compute relies on nova-conductor's rpc to be initialized This fix is totally safe and won't influence on other services. Change-Id: I9d7b682df4d411af24a1ff6bcad79697e32fa723 Partially-Implements: blueprint zeromq
This commit is contained in:
parent
d3ca1418c4
commit
26ac3d7ebb
2
lib/nova
2
lib/nova
@ -769,8 +769,8 @@ function start_nova_rest {
|
|||||||
}
|
}
|
||||||
|
|
||||||
function start_nova {
|
function start_nova {
|
||||||
start_nova_compute
|
|
||||||
start_nova_rest
|
start_nova_rest
|
||||||
|
start_nova_compute
|
||||||
}
|
}
|
||||||
|
|
||||||
function stop_nova_compute {
|
function stop_nova_compute {
|
||||||
|
13
stack.sh
13
stack.sh
@ -1030,6 +1030,14 @@ if is_service_enabled key; then
|
|||||||
fi
|
fi
|
||||||
|
|
||||||
|
|
||||||
|
# ZeroMQ
|
||||||
|
# ------
|
||||||
|
if is_service_enabled zeromq; then
|
||||||
|
echo_summary "Starting zeromq receiver"
|
||||||
|
run_process zeromq "$OSLO_BIN_DIR/oslo-messaging-zmq-receiver"
|
||||||
|
fi
|
||||||
|
|
||||||
|
|
||||||
# Horizon
|
# Horizon
|
||||||
# -------
|
# -------
|
||||||
|
|
||||||
@ -1208,11 +1216,6 @@ if is_service_enabled nova; then
|
|||||||
iniset $NOVA_CONF keymgr fixed_key $(generate_hex_string 32)
|
iniset $NOVA_CONF keymgr fixed_key $(generate_hex_string 32)
|
||||||
fi
|
fi
|
||||||
|
|
||||||
if is_service_enabled zeromq; then
|
|
||||||
echo_summary "Starting zermomq receiver"
|
|
||||||
run_process zeromq "$OSLO_BIN_DIR/oslo-messaging-zmq-receiver"
|
|
||||||
fi
|
|
||||||
|
|
||||||
# Launch the nova-api and wait for it to answer before continuing
|
# Launch the nova-api and wait for it to answer before continuing
|
||||||
if is_service_enabled n-api; then
|
if is_service_enabled n-api; then
|
||||||
echo_summary "Starting Nova API"
|
echo_summary "Starting Nova API"
|
||||||
|
Loading…
Reference in New Issue
Block a user