7e076b39a4
It's supposed that online migrations are executed once services are upgraded and restarted after upgrade. Eventually, you can run online migrations before the next upgrade according to the doc [1] So we move that to a separate file that is executed after all services are upgraded and handlers are flushed. Tasks are delegated to API hosts and we clean up facts for them as well. [1] https://docs.openstack.org/cinder/latest/admin/upgrades.html#database-upgrades Change-Id: Ic3ecdddd7dcc2dd617c8606278590c8e59230fdf
21 lines
756 B
YAML
21 lines
756 B
YAML
---
|
|
# Copyright 2014, Rackspace US, Inc.
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
- name: Perform a cinder DB sync
|
|
command: "{{ cinder_bin }}/cinder-manage db sync"
|
|
become: yes
|
|
become_user: "{{ cinder_system_user_name }}"
|
|
changed_when: false
|