From c8f8b301243d9e63353e96ba30e7b0de5f874e7a Mon Sep 17 00:00:00 2001
From: Mark Goddard <mark@stackhpc.com>
Date: Wed, 13 Mar 2019 09:37:03 +0000
Subject: [PATCH] Separate placement DB sync and data migrations

For an online upgrade, these commands should be executed separately.

Change-Id: I8d40a4d66c18022e73b48ecdfd299d9ed459777f
---
 docker/placement/placement-api/extend_start.sh | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docker/placement/placement-api/extend_start.sh b/docker/placement/placement-api/extend_start.sh
index f69b2eb8a7..65a2ca0e51 100644
--- a/docker/placement/placement-api/extend_start.sh
+++ b/docker/placement/placement-api/extend_start.sh
@@ -8,6 +8,18 @@ if [[ "${!KOLLA_BOOTSTRAP[@]}" ]]; then
     exit 0
 fi
 
+# DB synchronisation. To be executed prior to upgrading services.
+if [[ "${!KOLLA_UPGRADE[@]}" ]]; then
+    placement-manage db sync
+    exit 0
+fi
+
+# Online data migrations. To be executed after upgrading services.
+if [[ "${!KOLLA_OSM[@]}" ]]; then
+    placement-manage db online_data_migrations
+    exit 0
+fi
+
 # NOTE(pbourke): httpd will not clean up after itself in some cases which
 # results in the container not being able to restart. (bug #1489676, 1557036)
 if [[ "${KOLLA_BASE_DISTRO}" =~ debian|ubuntu ]]; then