From 7f1ba57e1868cab599f3f8fb2731fe4663428462 Mon Sep 17 00:00:00 2001
From: Duong Ha-Quang <duonghq@vn.fujitsu.com>
Date: Wed, 4 Apr 2018 15:19:49 +0700
Subject: [PATCH] Apply Nova rolling upgrade logic

This patchset apply Nova rolling upgrade logic [1]

[1] https://docs.openstack.org/nova/latest/user/upgrade.html

Change-Id: I2cc973896d08988c0db121673d357fd1d37e6e6c
Implements: blueprint apply-service-upgrade-procedure
---
 docker/nova/nova-api/extend_start.sh | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/docker/nova/nova-api/extend_start.sh b/docker/nova/nova-api/extend_start.sh
index df277923ab..dd18f798cb 100644
--- a/docker/nova/nova-api/extend_start.sh
+++ b/docker/nova/nova-api/extend_start.sh
@@ -9,6 +9,17 @@ if [[ "${!KOLLA_BOOTSTRAP[@]}" ]]; then
     exit 0
 fi
 
+if [[ "${!KOLLA_UPGRADE[@]}}" ]]; then
+    nova-manage db sync
+    nova-manage api_db sync
+    exit 0
+fi
+
+if [[ "${!KOLLA_OSM[@]}}" ]]; then
+    nova-manage db online_data_migrations
+    exit 0
+fi
+
 # Assume the service runs on top of Apache when user is root
 if [[ "$(whoami)" == 'root' ]]; then
     # NOTE(pbourke): httpd will not clean up after itself in some cases which