Handle upgrading cinder-volume under pacemaker
authorAlan Bishop <abishop@redhat.com>
Tue, 23 May 2017 14:42:24 +0000 (10:42 -0400)
committerAlan Bishop <abishop@redhat.com>
Fri, 26 May 2017 12:26:49 +0000 (08:26 -0400)
commitc4e3bbe039135f32f0e198365e704b3dbfd00290
treea4d2bdbec6c63c4e0156f57bea4c8917d4105fd8
parent9c93a1aff67eff1b32aa0a7d04d6f86afe8ae071
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
puppet/services/pacemaker/cinder-volume.yaml