1. Move minor upgrade content from the install guide to the upgrade guide 2. Revise the overview section to include minor upgrades 3. Restructure the upgrade guide for improved information flow 4. Add configure-keystone.rst to the old install guide that was accidently removed in https://review.openstack.org/#/c/328095/ Change-Id: I602ef4a4f95f5ff46ee9b9eaaaa6ccdfd637d1dc Implements: blueprint osa-install-guide-overhaul
1.3 KiB
Overview
An OpenStack-Ansible environment can be upgraded between minor versions, and between major versions.
Upgrades between minor versions of OpenStack-Ansible require updating
the repository clone to the latest minor release tag, then running
playbooks against the target hosts. For more information, see minor-upgrades
.
For major upgrades, the OpenStack-Ansible repository provides
playbooks and scripts used to upgrade an environment. The
run-upgrade.sh
script runs each upgrade playbook in the
correct order, or playbooks can be run individually if necessary.
Alternatively, a deployer can upgrade manually. A major upgrade process
performs the following actions:
- Modifies files residing in
/etc/openstack_deploy
in order to reflect new configuration values. - 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. - Upgrade the RabbitMQ server during an OpenStack-Ansible upgrade
process. See
setup-infra-playbook
for details.
For more information on the major upgrade process, see script-upgrade
and manual-upgrade
.
Note
You can only upgrade between sequential releases.