aboutsummaryrefslogtreecommitdiffstats
path: root/ci/environments/scenario001-multinode.yaml
diff options
context:
space:
mode:
authorSteven Hardy <shardy@redhat.com>2017-01-18 17:50:35 +0000
committerSteven Hardy <shardy@redhat.com>2017-01-19 13:27:58 +0000
commitdf1e016ad75ae82d163e20600d3779932a24153b (patch)
tree76be0d07392a7d3fab5b61e3de4798387d0817bc /ci/environments/scenario001-multinode.yaml
parentd5d8701c458450fe9f40ff1e421aa38d39c21c12 (diff)
Don't start all services during upgrade steps
Currently we start all OpenStack services in step6, but puppet already does this, and sometimes services require configuration to account for the new version after the yum update before they will start. So instead of reimplementing that configuration management in ansible, just defer starting the services until puppet has run which will happen right after the ansible upgrade steps complete. Note there are some DB sync operations etc that we may also be able to remove and let puppet do those steps, but I've left those in for now, as we know there are some actions during that phase e.g nova cells setup, which aren't yet handled by puppet. Change-Id: Idc8e253167a4bc74b086830cfabf28d4aab97d28
Diffstat (limited to 'ci/environments/scenario001-multinode.yaml')
0 files changed, 0 insertions, 0 deletions