315780f350
Boss drum, motivating rhythm of life with the healing, rhythmic synergy. More seriously, this patch re-arranges the documentation structure to conform to the structure outlined in [1]. With it, some changes are made to effectively transition the links and simplify the sphinx configuration. The Mitaka/Liberty documentation links are removed as they are no longer available. [1] http://specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration.html Change-Id: Icc985de3af4de5ea7a5aa01b6e6f6e524c67f11b
31 lines
1.2 KiB
ReStructuredText
31 lines
1.2 KiB
ReStructuredText
========
|
|
Overview
|
|
========
|
|
|
|
An OpenStack-Ansible environment can upgrade to a minor or a major version.
|
|
|
|
.. note::
|
|
|
|
You can only upgrade between sequential releases.
|
|
|
|
Upgrades between minor versions of OpenStack-Ansible require
|
|
updating the repository clone to the latest minor release tag, and then
|
|
running playbooks against the target hosts. For more information, see
|
|
:ref:`upgrading-to-a-minor-version`.
|
|
|
|
For upgrades between major versions, the OpenStack-Ansible repository provides
|
|
playbooks and scripts 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 the ``/etc/openstack_deploy`` directory, to
|
|
reflect new configuration values.
|
|
- Places flag files that are created by the migration scripts in order to
|
|
achieve idempotency. These files are placed in the |upgrade_backup_dir|
|
|
directory.
|
|
- Upgrades the RabbitMQ server. See :ref:`setup-infra-playbook` for details.
|
|
|
|
For more information about the major upgrade process, see
|
|
:ref:`upgrading-by-using-a-script` and :ref:`upgrading-manually`.
|