openstack
/
charm-deployment-guide
Code Issues Proposed changes

Merge "Add detail to openstack upgrades"

This commit is contained in:
Zuul 2021-03-30 16:15:11 +00:00 committed by Gerrit Code Review
parent c92b49a48c 4f0677ffae
commit a2f7f2e181
1 changed files with 41 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

65
deploy-guide/source/upgrade-openstack.rst
View File

@ -250,22 +250,39 @@ The order provided below is the order used by internal testing.
Software sources Software sources
---------------- ----------------
The essence of an OpenStack upgrade is a change of a machine's software sources A key part of an OpenStack upgrade is the stipulation of a unit's software
so that a more recent combination of Ubuntu release (series) and OpenStack sources. For an upgrade, the latter will naturally reflect a more recent
release is used. This combination is based on the `Ubuntu Cloud Archive`_ and combination of Ubuntu release (series) and OpenStack release. This combination
translates to a "cloud archive OpenStack release". It takes on the following is based on the `Ubuntu Cloud Archive`_ and translates to a "cloud archive
syntax: OpenStack release". It takes on the following syntax:
``<ubuntu series>-<openstack-release>`` ``<ubuntu series>-<openstack-release>``
This becomes the value given to a charm's ``openstack-origin`` configuration The value is passed to a charm's ``openstack-origin`` configuration option. For
option. For example, to select the 'bionic-train' release: example, to select the 'focal-victoria' release:
``openstack-origin=cloud:bionic-train`` ``openstack-origin=cloud:focal-victoria``
.. important:: In this way the charm is informed on where to find updates for the packages
that it is responsible for.
The series must correspond to the series currently in use. .. note::
A few charms use option ``source`` instead of ``openstack-origin``. See the
next section.
Notes concerning the value of ``openstack-origin``:
* The default is 'distro'. This denotes an Ubuntu release's default archive
(e.g. in the case of the focal series it corresponds to OpenStack Ussuri).
The value of 'distro' is therefore invalid in the context of an OpenStack
upgrade.
* It should normally be the same across all charms.
* Its series component must be that of the series currently in use (i.e. a
series upgrade and an OpenStack upgrade are two completely separate
procedures).
.. _perform_the_upgrade: .. _perform_the_upgrade:
@ -288,8 +305,8 @@ application has a sole unit.
.. attention:: .. attention::
The "all-in-one" method should only be used when the charm does not The "all-in-one" method should only be used when the charm does not support
support the ``openstack-upgrade`` action. the ``openstack-upgrade`` action.
The syntax is: The syntax is:
@ -302,19 +319,19 @@ use the ``source`` charm option instead. The Ceph charms are a classic example:
.. code-block:: none .. code-block:: none
juju config ceph-mon source=cloud:bionic-train juju config ceph-mon source=cloud:focal-victoria
.. note:: .. note::
The ceph-osd and ceph-mon charms are able to maintain service availability The ceph-osd and ceph-mon charms are able to maintain service availability
during the upgrade. during the upgrade.
So to upgrade Cinder across all units (currently running Bionic) from Stein to So to upgrade Cinder across all units (currently running Focal) from Ussuri to
Train: Victoria:
.. code-block:: none .. code-block:: none
juju config cinder openstack-origin=cloud:bionic-train juju config cinder openstack-origin=cloud:focal-victoria
Single-unit Single-unit
~~~~~~~~~~~ ~~~~~~~~~~~
@ -338,13 +355,13 @@ also be discovered via the CLI:
juju run --application <application-name> is-leader juju run --application <application-name> is-leader
For example, to upgrade a three-unit glance application from Stein to Train For example, to upgrade a three-unit glance application from Ussuri to Victoria
where ``glance/1`` is the leader: where ``glance/1`` is the leader:
.. code-block:: none .. code-block:: none
juju config glance action-managed-upgrade=True juju config glance action-managed-upgrade=True
juju config glance openstack-origin=cloud:bionic-train juju config glance openstack-origin=cloud:focal-victoria
juju run-action --wait glance/1 openstack-upgrade juju run-action --wait glance/1 openstack-upgrade
juju run-action --wait glance/0 openstack-upgrade juju run-action --wait glance/0 openstack-upgrade
@ -373,13 +390,13 @@ by the operator.
The "paused-single-unit" method is the recommended OpenStack service upgrade The "paused-single-unit" method is the recommended OpenStack service upgrade
method. method.
For example, to upgrade a three-unit nova-compute application from Stein to For example, to upgrade a three-unit nova-compute application from Ussuri to
Train where ``nova-compute/0`` is the leader: Victoria where ``nova-compute/0`` is the leader:
.. code-block:: none .. code-block:: none
juju config nova-compute action-managed-upgrade=True juju config nova-compute action-managed-upgrade=True
juju config nova-compute openstack-origin=cloud:bionic-train juju config nova-compute openstack-origin=cloud:focal-victoria
juju run-action --wait nova-compute/0 pause juju run-action --wait nova-compute/0 pause
juju run-action --wait nova-compute/0 openstack-upgrade juju run-action --wait nova-compute/0 openstack-upgrade
@ -403,13 +420,13 @@ flow to the associated parent unit while its upgrade is underway.
take advantage of the "pause-single-unit" method's ability to pause it take advantage of the "pause-single-unit" method's ability to pause it
before upgrading the parent unit. before upgrading the parent unit.
For example, to upgrade a three-unit keystone application from Stein to Train For example, to upgrade a three-unit keystone application from Ussuri to
where ``keystone/2`` is the leader: Victoria where ``keystone/2`` is the leader:
.. code-block:: none .. code-block:: none
juju config keystone action-managed-upgrade=True juju config keystone action-managed-upgrade=True
juju config keystone openstack-origin=cloud:bionic-train juju config keystone openstack-origin=cloud:focal-victoria
juju run-action --wait keystone-hacluster/1 pause juju run-action --wait keystone-hacluster/1 pause
juju run-action --wait keystone/2 pause juju run-action --wait keystone/2 pause