The rabbitmq playbook is designed to run in parallel across the cluster.
This causes an issue when upgrading rabbitmq to a new major or minor
version because RabbitMQ does not support doing an online migration of
datasets between major versions. while a minor release can be upgrade
while online it is recommended to bring down the cluster to do any
upgrade actions. The current configuration takes no account of this.
* A new variable has been added called `rabbitmq_upgrade`. This is set to
false by default to prevent a new version being installed unintentionally.
To run the upgrade, which will shutdown the cluster, the variable can be
set to true on the commandline:
* A new variable has been added called `rabbitmq_ignore_version_state`
which can be set "true" to ignore the package and version state tasks.
This has been provided to allow a deployer to rerun the plays in an
environment where the playbooks have been upgraded and the default
version of rabbitmq has changed within the role and the deployer has
elected to upgraded the installation at that time. This will ensure a
deployer is able to recluster an environment as needed without
effecting the package state.
* A new variable has been added `rabbitmq_primary_cluster_node` which
allows a deployer to elect / set the primary cluster node in an
environment. This variable is used to determine the restart order
of RabbitMQ nodes. IE this will be the last node down and first one
up in an environment. By default this variable is set to:
rabbitmq_primary_cluster_node: "{{ groups['rabbitmq_all'][0] }}"
scripts/run-upgrade.sh has been modified to pass 'rabbitmq_upgrade=true'
on the command line so that RabbitMQ can be upgraded as part of the
upgrade between OpenStack versions.
DocImpact
Change-Id: I17d4429b9b94d47c1578dd58a2fb20698d1fe02e
Closes-bug: #1474992
(cherry picked from commit 6ea86e6274bedaff955d734222c9f4b1cc2c3a2a)
Reviewed: https:/ /review. openstack. org/204680 /git.openstack. org/cgit/ stackforge/ os-ansible- deployment/ commit/ ?id=24300d361d7 f5828992cddbb5c 80b03249a7e9ba
Committed: https:/
Submitter: Jenkins
Branch: kilo
commit 24300d361d7f582 8992cddbb5c80b0 3249a7e9ba
Author: git-harry <email address hidden>
Date: Thu Jul 16 11:01:13 2015 +0100
Fix rabbitmq playbook to allow upgrades
The rabbitmq playbook is designed to run in parallel across the cluster.
This causes an issue when upgrading rabbitmq to a new major or minor
version because RabbitMQ does not support doing an online migration of
datasets between major versions. while a minor release can be upgrade
while online it is recommended to bring down the cluster to do any
upgrade actions. The current configuration takes no account of this.
Reference: /www.rabbitmq. com/clustering. html#upgrading for further details.
https:/
* A new variable has been added called `rabbitmq_upgrade`. This is set to
false by default to prevent a new version being installed unintentionally.
To run the upgrade, which will shutdown the cluster, the variable can be
set to true on the commandline:
Example:
openstack- ansible -e rabbitmq_ upgrade= true \
rabbitmq- install. yml
* A new variable has been added called `rabbitmq_ ignore_ version_ state`
which can be set "true" to ignore the package and version state tasks.
This has been provided to allow a deployer to rerun the plays in an
environment where the playbooks have been upgraded and the default
version of rabbitmq has changed within the role and the deployer has
elected to upgraded the installation at that time. This will ensure a
deployer is able to recluster an environment as needed without
effecting the package state.
Example:
openstack- ansible -e rabbitmq_ ignore_ version_ state=true \
rabbitmq- install. yml
* A new variable has been added `rabbitmq_ primary_ cluster_ node` which primary_ cluster_ node: "{{ groups[ 'rabbitmq_ all'][0] }}"
allows a deployer to elect / set the primary cluster node in an
environment. This variable is used to determine the restart order
of RabbitMQ nodes. IE this will be the last node down and first one
up in an environment. By default this variable is set to:
rabbitmq_
scripts/ run-upgrade. sh has been modified to pass 'rabbitmq_ upgrade= true'
on the command line so that RabbitMQ can be upgraded as part of the
upgrade between OpenStack versions.
DocImpact 7c1578dd58a2fb2 0698d1fe02e f955d734222c9f4 b1cc2c3a2a)
Change-Id: I17d4429b9b94d4
Closes-bug: #1474992
(cherry picked from commit 6ea86e6274bedaf