starlingx/config
Code Issues Proposed changes

tsconfig: Move scripts into tsconfig

Browse Source 
Currently the build system automagically copies the scripts directory
into tsconfig as part of constructing the source rpm. In order to
build with OBS (for multi-os), all the files need to be in the correct
directory level, in this case update/tsconfig/tsconfig.

Correct where devstack finds the tsconfig script

Tested with current build-pkgs from clean and verified contents of
both tsconfig RPM and SRPM where correct.

Depends-On: I58dc94eaac98a87509f57fdd2126188a6917569c
Change-Id: Ib6fdf7aaad5ed91be091b7f1f63365895a8aea7d
Signed-off-by: Saul Wold <sgw@linux.intel.com>
This commit is contained in:
Saul Wold
2019-06-04 09:24:23 -07:00
committed by Scott Little
parent e06a8260c1
commit 925615fbe3
2 changed files with 0 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

49
tsconfig/tsconfig/scripts/tsconfig Normal file
View File

@@ -0,0 +1,49 @@
. /etc/build.info
#
# Keep the following path and flag declarations in sync with tsconfig.py
#
# Platform configuration paths and files
PLATFORM_CONF_PATH=/etc/platform
PLATFORM_CONF_FILE=${PLATFORM_CONF_PATH}/platform.conf
PLATFORM_SIMPLEX_FLAG=${PLATFORM_CONF_PATH}/simplex
VOLATILE_PATH=/var/run
PLATFORM_PATH=/opt/platform
CONFIG_PATH=${PLATFORM_PATH}/config/${SW_VERSION}
PUPPET_PATH=${PLATFORM_PATH}/puppet/${SW_VERSION}
CGCS_PATH=/opt/cgcs
# System configuration flags
INITIAL_CONFIG_COMPLETE_FLAG=${PLATFORM_CONF_PATH}/.initial_config_complete
# Worker configuration flags
# Set after the first application of worker manifests
INITIAL_WORKER_CONFIG_COMPLETE=${PLATFORM_CONF_PATH}/.initial_worker_config_complete
# Set after each application of worker manifests
VOLATILE_WORKER_CONFIG_COMPLETE=${VOLATILE_PATH}/.worker_config_complete
# Set to prevent starting worker services (used in combined node upgrade)
VOLATILE_DISABLE_WORKER_SERVICES=${VOLATILE_PATH}/.disable_worker_services
# Upgrade flags
# Set on controller-0 to force controller-1 to do an upgrade after install.
CONTROLLER_UPGRADE_FLAG=${PLATFORM_CONF_PATH}/.upgrade_controller_1
# Set on controller-0 (by controller-1) to indicate a completed upgrade.
CONTROLLER_UPGRADE_COMPLETE_FLAG=${PLATFORM_CONF_PATH}/.upgrade_controller_1_complete
# Set on controller-0 (by controller-1) to indicate a failed upgrade data migration
CONTROLLER_UPGRADE_FAIL_FLAG=${PLATFORM_CONF_PATH}/.upgrade_controller_1_fail
# Set on controller-1 to indicate we are rolling back the upgrade
UPGRADE_ROLLBACK_FLAG=${PLATFORM_CONF_PATH}/.upgrade_rollback
# Set on controller-1 to indicate we are aborting the upgrade
UPGRADE_ABORT_FILE=.upgrade_abort
UPGRADE_ABORT_FLAG=${CONFIG_PATH}/${UPGRADE_ABORT_FILE}
# Set on controller-0 (by controller-1) to indicate that data migration has started
CONTROLLER_UPGRADE_STARTED_FLAG=${PLATFORM_CONF_PATH}/.upgrade_controller_1_started
# Backup / Restore flags
BACKUP_IN_PROGRESS_FLAG=${PLATFORM_CONF_PATH}/.backup_in_progress
RESTORE_IN_PROGRESS_FLAG=${PLATFORM_CONF_PATH}/.restore_in_progress