openstack/kolla
Code Issues Proposed changes

Separate placement DB sync and data migrations

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

Change-Id: I8d40a4d66c18022e73b48ecdfd299d9ed459777f
This commit is contained in:
Mark Goddard 2019-03-13 09:37:03 +00:00
parent 8c99d5300e
commit c8f8b30124
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docker/placement/placement-api/extend_start.sh
View File

@ -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