Fixup systemctl_swift stop/start during the controller upgrade
authormarios <marios@redhat.com>
Wed, 9 Mar 2016 13:43:40 +0000 (15:43 +0200)
committermarios <marios@redhat.com>
Wed, 9 Mar 2016 13:43:40 +0000 (15:43 +0200)
commit9727a27d00bbc423b565e02d2d69cc3d74f96761
tree1901fe2119e009abbfdae43061b2d81e0f3e9b0f
parent2cc592d29d932e64708e20b8ff10f30c80c99249
Fixup systemctl_swift stop/start  during the controller upgrade

During the controller upgrade in
major_upgrade_controller_pacemaker_1.sh we use systemctl to stop
all swift services and then start them again in _pacemaker_2.sh

In the case of stand-alone swift nodes the deployer may have
used the ControllerEnableSwiftStorage: false so that only the
swift-proxy service is left on controllers (wrt swift). The
systemctl_swift function used during upgrades is changed to factor
this in.

Change-Id: Ib22005123429f250324df389855d0dccd2343feb
extraconfig/tasks/pacemaker_common_functions.sh