From b1b869d9e985438a8794f43fb8d94cb6608cd80d Mon Sep 17 00:00:00 2001 From: "jing.liuqing" Date: Fri, 23 Jun 2017 08:33:16 +0800 Subject: [PATCH] Run conductor before tacker server Logically, mistral services and conductor are dependents of tacker server, so they should be started before it. Change-Id: Iac2b7344764fc9e23f51677eaf44f6e83684a370 Implements: blueprint refactor-vim-monitor --- devstack/lib/tacker | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/devstack/lib/tacker b/devstack/lib/tacker index ded9e0032..d33c38541 100644 --- a/devstack/lib/tacker +++ b/devstack/lib/tacker @@ -152,6 +152,8 @@ function start_tacker { service_port=$TACKER_PORT_INT service_protocol="http" fi + # Start tacker conductor + run_process tacker-conductor "$TACKER_BIN_DIR/tacker-conductor $cfg_file_options" # Start the Tacker service run_process tacker "$TACKER_BIN_DIR/tacker-server $cfg_file_options" echo "Waiting for Tacker to start..." @@ -165,8 +167,6 @@ function start_tacker { if is_service_enabled tls-proxy; then start_tls_proxy '*' $TACKER_PORT $TACKER_HOST $TACKER_PORT_INT & fi - # Start tacker conductor - run_process tacker-conductor "$TACKER_BIN_DIR/tacker-conductor $cfg_file_options" } # stop_tacker() - Stop running processes (non-screen)