From 2be3e4e7cc6740dd8657c019cc5e97e63a9d0132 Mon Sep 17 00:00:00 2001
From: Duong Ha-Quang <duonghq@vn.fujitsu.com>
Date: Thu, 21 Dec 2017 18:15:50 +0700
Subject: [PATCH] Apply Cinder rolling upgrade

Apply Cinder database migration procedure:

[1] https://docs.openstack.org/cinder/pike/upgrade.html

Change-Id: I9a847b0a916a85d8f2622e93734330da5122f0d8
---
 docker/cinder/cinder-api/extend_start.sh | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docker/cinder/cinder-api/extend_start.sh b/docker/cinder/cinder-api/extend_start.sh
index f56c0cd5e8..7fef2609bd 100644
--- a/docker/cinder/cinder-api/extend_start.sh
+++ b/docker/cinder/cinder-api/extend_start.sh
@@ -8,6 +8,15 @@ if [[ "${!KOLLA_BOOTSTRAP[@]}" ]]; then
     exit 0
 fi
 
+if [[ "${!KOLLA_OSM[@]}" ]]; then
+    if [[ -z ${MAX_NUMBER} ]]; then
+        cinder-manage db online_data_migrations --max_count ${MAX_NUMBER}
+    else
+        cinder-manage db online_data_migrations
+    fi
+    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