Browse Source

Handle upgrading cinder-volume under pacemaker

Add upgrade tasks for cinder-volume when it's controlled by pacemaker:

o Stop the service before the entire pacemaker cluster is stopped.
  This ensures the service is stopped before infrastructure services
  (e.g. rabbitmq) go away.
o Migrate the cinder DB prior to restarting the service. This covers
  the situation when puppet-cinder (who otherwise would handle the db
  sync) isn't managing the service.
o Start the service after the rest of the pacemaker cluster has been
  started.

Closes-Bug: #1691851
Change-Id: I5874ab862964fadb68320d5c4de39b20f53dc25c
changes/80/467280/4
Alan Bishop 5 years ago
parent
commit
c4e3bbe039
  1. 15
      puppet/services/pacemaker/cinder-volume.yaml

15
puppet/services/pacemaker/cinder-volume.yaml

@ -54,3 +54,18 @@ outputs:
cinder::host: hostgroup
step_config:
include ::tripleo::profile::pacemaker::cinder::volume
upgrade_tasks:
- name: Stop cinder_volume service (pacemaker)
tags: step1
pacemaker_resource:
resource: openstack-cinder-volume
state: disable
wait_for_resource: true
- name: Sync cinder DB
tags: step5
command: cinder-manage db sync
- name: Start cinder_volume service (pacemaker)
tags: step5
pacemaker_resource:
resource: openstack-cinder-volume
state: enable

Loading…
Cancel
Save