6442320b24
The documentation has currently multiple problems: - The top left tag of the openstacktheme isn't consistent with the latest available tag, which confuses people (see related bug) - There are unused variables that could deserve cleanup - There are static content that can be discovered from files - We don't leverage the dynamic nature of the configuration for conditional upgrade messages, while we should. Change-Id: If8776ee54fda5cdcc27be36e2031150914aa32b2 Related-Bug: #1755241
30 lines
745 B
ReStructuredText
30 lines
745 B
ReStructuredText
.. _upgrading-by-using-a-script:
|
|
|
|
Upgrading by using a script
|
|
===========================
|
|
|
|
The |current_release_formal_name| release series of OpenStack-Ansible contains
|
|
the code for migrating from |previous_release_formal_name| to
|
|
|current_release_formal_name|.
|
|
|
|
Running the upgrade script
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
To upgrade from |previous_release_formal_name| to |current_release_formal_name|
|
|
by using the upgrade script, perform the following steps in the
|
|
``openstack-ansible`` directory:
|
|
|
|
#. Change directory to the repository clone root directory:
|
|
|
|
.. code-block:: console
|
|
|
|
# cd /opt/openstack-ansible
|
|
|
|
#. Run the following commands:
|
|
|
|
.. parsed-literal::
|
|
|
|
# git checkout |latest_tag|
|
|
# ./scripts/run-upgrade.sh
|
|
|