diff options
| author |   marios <marios@redhat.com> | 2016-03-09 15:43:40 +0200 |
|---|---|---|
| committer | marios <marios@redhat.com> | 2016-03-09 15:43:40 +0200 |
| commit | 9727a27d00bbc423b565e02d2d69cc3d74f96761 (patch) | |
| tree | 1901fe2119e009abbfdae43061b2d81e0f3e9b0f /puppet/extraconfig/pre_deploy/per_node.yaml | |
| parent | 2cc592d29d932e64708e20b8ff10f30c80c99249 (diff) | |
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
Diffstat (limited to 'puppet/extraconfig/pre_deploy/per_node.yaml')
0 files changed, 0 insertions, 0 deletions