grenade/upgrade-devstack
Mauro S. M. Rodrigues ac53d2c3f9 Modify upgrade-* scripts to allow skip configuration if not needed
This allow grenade to move and test from a brand new release to master without
any change.

This way it allows to enable d-g grenade testing new-release->master where for
a just released Openstack means that we don't need any new configuration yet.

Change-Id: I3e685deb61b95116420eae9cacb6b38dc405ffe9
2013-12-10 11:46:02 +00:00

48 lines
1.0 KiB
Bash
Executable File

#!/usr/bin/env bash
# ``upgrade-devstack``
# Keep track of the grenade directory
GRENADE_DIR=$(cd $(dirname "$0") && pwd)
# Import common functions
source $GRENADE_DIR/functions
# Determine what system we are running on. This provides ``os_VENDOR``,
# ``os_RELEASE``, ``os_UPDATE``, ``os_PACKAGE``, ``os_CODENAME``
# and ``DISTRO``
GetDistro
# Source params
source $GRENADE_DIR/grenaderc
# For debugging
set -o xtrace
# Upgrade DevStack
# ================
# calls upgrade-devstack for specific release
upgrade_project devstack $GRENADE_DIR $BASE_DEVSTACK_BRANCH
# Preserve accrc files for future usage
cp -a $BASE_DEVSTACK_DIR/accrc $TARGET_DEVSTACK_DIR/accrc
# Translate Services
# ------------------
#BASE_ENABLED_SERVICES=$(source $BASE_DEVSTACK_DIR/stackrc; echo $ENABLED_SERVICES)
#ENABLED_SERVICES=""
# NOOP for now!
# Write new config to target DevStack
#echo -e "\nENABLED_SERVICES=$ENABLED_SERVICES" >>$TARGET_DEVSTACK_DIR/localrc
# Handle Defaults Changes
# -----------------------
# NOOP for now!