From 4f4de70594d3d9060c262438ddd87f768b4dda00 Mon Sep 17 00:00:00 2001 From: Duong Ha-Quang Date: Thu, 17 May 2018 16:26:41 +0700 Subject: Only run rolling upgrade for neutron, vpnaas, fwaas Due to only neutron, vpnass and fwaas have supported for rolling upgrade database migration, this patch set add --subproject argument to limited the upgrade to these. Co-Authored-By: Ha Manh Dong Change-Id: I007e0068622fd630eb9f2f29b604015376ae7cd3 Implements: blueprint apply-service-upgrade-procedure --- docker/neutron/neutron-server/extend_start.sh | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) (limited to 'docker') diff --git a/docker/neutron/neutron-server/extend_start.sh b/docker/neutron/neutron-server/extend_start.sh index a7619c576..641679c1a 100644 --- a/docker/neutron/neutron-server/extend_start.sh +++ b/docker/neutron/neutron-server/extend_start.sh @@ -22,12 +22,18 @@ fi # of the KOLLA_UPGRADE variable being set, including empty. if [[ "${!KOLLA_UPGRADE[@]}" ]]; then if [[ "${!NEUTRON_DB_EXPAND[@]}" ]]; then + DB_ACTION="--expand" echo "Expanding database" - neutron-db-manage upgrade --expand fi if [[ "${!NEUTRON_DB_CONTRACT[@]}" ]]; then + DB_ACTION="--contract" echo "Contracting database" - neutron-db-manage upgrade --contract + fi + + if [[ "${!NEUTRON_ROLLING_UPGRADE_SERVICES[@]}" ]]; then + for service in ${NEUTRON_ROLLING_UPGRADE_SERVICES}; do + neutron-db-manage --subproject $service upgrade $DB_ACTION + done fi exit 0 fi -- cgit v1.2.3