openstack/tacker
Code Issues Proposed changes

Run conductor before tacker server

Browse Source 
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
This commit is contained in:
jing.liuqing
2017-06-23 08:33:16 +08:00
parent 40261e5b11
commit b1b869d9e9
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
devstack/lib/tacker
View File

@@ -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)