Upgrade of Cinder block storage nodes
authorJiri Stransky <jistr@redhat.com>
Thu, 3 Mar 2016 10:36:02 +0000 (11:36 +0100)
committerJiri Stransky <jistr@redhat.com>
Thu, 3 Mar 2016 10:49:34 +0000 (11:49 +0100)
commit7455f1afc3d2272a60d93672018324926c9eaa0d
tree2874d114c49e0fa34e5f078d367eb136f3598785
parentf496aa225c2f12e2f8da80c74d4b511e0e6e2bf0
Upgrade of Cinder block storage nodes

This introduces upgrades for Cinder block storage nodes. Currently
Cinder doesn't support upgrade level pinning and cannot safely deal with
version skew. This means that we have to upgrade Cinder storage nodes in
sync with controller nodes (after they were taken down for upgrade,
before they are brought back up) to ensure that Cinder services perform
AMQP communication only within the same major version of Cinder.

According to our current knowledge, Cinder block storage nodes are the
only node type that will have to be upgraded in sync with controllers.

Change-Id: Icec913c015eff744b0f31b513176b4b657df43af
extraconfig/tasks/major_upgrade_block_storage.sh [new file with mode: 0644]
extraconfig/tasks/major_upgrade_pacemaker.yaml