Alexandra 3bb1c40f72 DOCS: Clean up of the Newton upgrade guide

Forming to conventions applied in the install guide.
This cleans up RST, spelling, and grammar fixes.

Change-Id: Ieeb678bffc2b59a29e05528cc3d908b036e6c1a8
(cherry picked from commit 29ec1bad24)

2016-05-26 10:22:27 +01:00

1.8 KiB

Raw Blame History

Overview

The OpenStack-Ansible repository provides playbooks and scripts used to upgrade an environment from Mitaka to Newton. The run-upgrade.sh script runs each upgrade playbook in the correct order, or playbooks can be run individually if necessary.

Running the upgrade script

The Newton release series of OpenStack-Ansible contain the code for migrating from Mitaka to Newton.

Warning

The upgrade script is still under active development and should not be run at this time.

To upgrade from Mitaka to Newton using the upgrade script, perform the following steps in the openstack-ansible directory:

# git checkout stable/newton
# LATEST_TAG=$(git describe --abbrev=0 --tags)
# git checkout ${LATEST_TAG}
# ./scripts/run-upgrade.sh

Upgrading manually

Deployers can run the upgrade steps manually. See manual-upgrade. Manual execution is useful for scoping the changes in the upgrade process (For example, in very large deployments with strict SLA requirements), or for inclusion into other orchestration for upgrade automation beyond what OpenStack-Ansible provides.

Upgrade actions

Both the upgrade script and manual upgrade steps perform the actions and use the concepts introduced below.

Configuration changes

The upgrade process modifies files residing in /etc/openstack_deploy in order to reflect new Newton values.

Flag files

Some flag files are created by the migration scripts in order to achieve idempotency. These files are placed in the /etc/openstack_deploy.NEWTON directory.

RabbitMQ upgrade

Upgrade the RabbitMQ server during an OpenStack-Ansible upgrade.

See setup-infra-playbook for details.

1.8 KiB Raw Blame History