OpenStack upgrade¶
This document outlines how to upgrade the OpenStack service components of a Charmed OpenStack cloud.
Warning
Upgrading an OpenStack cloud is not risk-free. The procedures outlined in this guide should first be tested in a pre-production environment.
Please read the Upgrades overview page before continuing.
Note
The charms only support single-step OpenStack upgrades (N+1). That is, to upgrade two releases forward you need to upgrade twice. You cannot skip releases when upgrading OpenStack with charms.
It may be worthwhile to read the upstream OpenStack Upgrades guide.
Software sources¶
A key part of an OpenStack upgrade is the stipulation of a unit’s software sources. For an upgrade, the latter will naturally reflect a more recent combination of Ubuntu release (series) and OpenStack release. This combination is based on the Ubuntu Cloud Archive and translates to a “cloud archive OpenStack release”. It takes on the following syntax:
<ubuntu series>-<openstack-release>
The value is passed to a charm’s openstack-origin configuration option. For
example, to select the ‘focal-victoria’ release:
openstack-origin=cloud:focal-victoria
In this way the charm is informed on where to find updates for the packages that it is responsible for.
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).
Note
A few charms use option source instead of openstack-origin (both
options support identical values). The source option is used by charms
that don’t deploy an actual OpenStack service.
Upgradable services¶
Services whose software is not included in the Ubuntu Cloud Archive do not get upgraded during a charmed OpenStack upgrade. This software is upgraded by the administrator (on the units) using other means (e.g. manually via package utilities, the Landscape management tool, a snap, or as part of a series upgrade). Common charms where this applies are:
memcached
ntp
percona-cluster
mysql-innodb-cluster
mysql-router
rabbitmq-server
vault
Services that are associated with subordinate charms are upgradable but only
indirectly. They get upgraded along with their parent principal application.
Subordinate charms do not support the openstack-origin (or source)
configuration option that is, as will be shown, a pre-requisite for initiating
an OpenStack charm payload upgrade.
Prepare for the upgrade¶
Pay special attention to the below pre-upgrade preparatory and informational sections.
Release notes¶
The OpenStack Charms Release notes for the corresponding current and target versions of OpenStack must be consulted for any special instructions. In particular, pay attention to services and/or configuration options that may be retired, deprecated, or changed.
Manual intervention¶
By design, the latest stable charms will support the software changes related to the OpenStack services being upgraded. During the upgrade, the charms will also strive to preserve the existing configuration of their associated services.
However, there are still times when intervention on the part of the operator may be needed, such as when an OpenStack service is removed/added/replaced or when a software bug (in the charms or in upstream OpenStack) affecting the upgrade is present. The below resources cover these topics:
Ensure cloud node software is up to date¶
Every machine in the cloud, including containers, should have their software packages updated to ensure that the latest SRUs have been applied. This is done in the usual manner:
sudo apt update
sudo apt full-upgrade
Verify the current deployment¶
Confirm that the output for the juju status command of the current deployment is error-free. In addition, if monitoring is in use (e.g. Nagios), ensure that all alerts have been resolved. You may also consider running a battery of operational checks on the cloud.
This step is to make certain that any issues that are apparent after the upgrade are not due to pre-existing problems.
Perform the upgrade¶
Perform the upgrade by following the below sections.
Disable unattended-upgrades¶
When performing a service upgrade on a cloud node that hosts multiple principal
charms (e.g. nova-compute and ceph-osd), ensure that unattended-upgrades is
disabled on the underlying machine for the duration of the upgrade process.
This is to prevent the other services from being upgraded outside of Juju’s
control. On a cloud node run:
sudo dpkg-reconfigure -plow unattended-upgrades
Perform a backup of the service databases¶
Perform a backup of the cloud service databases by applying the mysqldump
action to any unit of the cloud’s database application. Be sure to select all
applicable databases; the commands provided are examples only.
The permissions on the remote backup directory will need to be adjusted in order to access the data. Take note that the transfer method presented here will capture all existing backups in that directory.
Important
Store the backup archive in a safe place.
The next two sections include the commands to run for the two possible database applications.
percona-cluster¶
The percona-cluster application requires a modification to its “strict mode” (see Percona strict mode for an understanding of the implications).
juju run-action --wait percona-cluster/0 set-pxc-strict-mode mode=MASTER
juju run-action --wait percona-cluster/0 mysqldump \
databases=aodh,cinder,designate,glance,gnocchi,horizon,keystone,neutron,nova,nova_api,nova_cell0,placement
juju run-action --wait percona-cluster/0 set-pxc-strict-mode mode=ENFORCING
juju run -u percona-cluster/0 -- sudo chmod o+rx /var/backups/mysql
juju scp -- -r percona-cluster/0:/var/backups/mysql .
juju run -u percona-cluster/0 -- sudo chmod o-rx /var/backups/mysql
mysql-innodb-cluster¶
juju run-action --wait mysql-innodb-cluster/0 mysqldump \
databases=cinder,designate,glance,gnocchi,horizon,keystone,neutron,nova,nova_api,nova_cell0,placement,vault
juju run -u mysql-innodb-cluster/0 -- sudo chmod o+rx /var/backups/mysql
juju scp -- -r mysql-innodb-cluster/0:/var/backups/mysql .
juju run -u mysql-innodb-cluster/0 -- sudo chmod o-rx /var/backups/mysql
Archive old database data¶
During the upgrade, database migrations will be run. This operation can be
optimised by first archiving any stale data (e.g. deleted instances). Do this
by running the archive-data action on any nova-cloud-controller unit:
juju run-action --wait nova-cloud-controller/0 archive-data
This action may need to be run multiple times until the action output reports ‘Nothing was archived’.
Purge old compute service entries¶
Old compute service entries for units which are no longer part of the model should be purged prior to upgrading. These entries will show as ‘down’ (and be hosted on machines no longer in the model) in the current list of compute services:
openstack compute service list
To remove a compute service:
openstack compute service delete <service-id>
List the upgrade order¶
Generally speaking, the upgrade order is determined by the idea of a dependency tree. Those services that have the most potential impact on other services are upgraded first and those services that have the least potential impact on other services are upgraded last.
In the below table, charms are listed in the order in which their corresponding OpenStack services should be upgraded. Each service represented by a charm will need to be upgraded individually. Note that since charms merely modify a machine’s apt sources, any co-located service will have their packages updated along with those of the service being targeted.
Warning
Ceph may require one of its options to be set prior to upgrading, and failure to consider this may result in a broken cluster. See the associated upgrade issue.
Note
At this time, only stable charms are listed in the upgrade order table.
Order |
Charm |
|---|---|
1 |
|
2 |
|
3 |
|
4 |
|
5 |
|
6 |
|
7 |
|
8 |
|
9 |
|
10 |
|
11 |
|
12 |
|
13 |
|
14 |
|
15 |
|
16 |
|
17 |
|
18 |
|
19 |
|
20 |
|
21 |
|
22 |
|
23 |
|
24 |
|
25 |
|
26 |
Important
The OVN control plane will not be available between the commencement of the ovn-central upgrade and the completion of the nova-compute upgrade.
Update the charm channel¶
Warning
This step is only performed for charms that follow a channel (see Charm types).
A charm’s channel needs to be updated according to the target OpenStack release. This is done as per the following syntax:
juju refresh --channel=<channel> <application>
For example, if the cloud is being upgraded to OpenStack Yoga then the keystone charm’s channel should be updated to ‘yoga/stable’:
juju refresh --channel=yoga/stable keystone
Charms whose services are not technically part of the OpenStack project will generally use a channel naming scheme that is not based on OpenStack release names. Here is the ovn-central charm:
juju refresh --channel=22.03/stable ovn-central
Perform the upgrade¶
There are three methods available for performing an OpenStack service upgrade, two of which have charm requirements in terms of supported actions. Each method also has advantages and disadvantages with regard to:
the time required to perform an upgrade
maintaining service availability during an upgrade
This table summarises the characteristics and requirements of each method:
Method |
Time |
Downtime |
Charm requirements (actions) |
|---|---|---|---|
all-in-one |
shortest |
most |
none |
single-unit |
medium |
medium |
|
paused-single-unit |
longest |
least |
|
For example, although the all-in-one method upgrades a service the fastest, it also has the greatest potential for service downtime.
Note
A charm’s supported actions can be listed with command juju actions <charm-name>.
All-in-one¶
The all-in-one method upgrades all application units simultaneously. This method must be used if the application has a sole unit.
Although it is the quickest route, it will also cause a temporary disruption of the corresponding service.
Important
Exceptionally, the ceph-osd and ceph-mon applications use the all-in-one method but their charms are able to maintain service availability during the upgrade.
The syntax is:
juju config <openstack-charm> openstack-origin=cloud:<cloud-archive-release>
For example, to upgrade Cinder across all units (currently running Focal) from Ussuri to Victoria:
juju config cinder openstack-origin=cloud:focal-victoria
Charms whose services are not technically part of the OpenStack project will
use the source charm option instead. The Ceph charms are a classic example:
juju config ceph-mon source=cloud:focal-victoria
Single-unit¶
The single-unit method builds upon the all-in-one method by allowing for the
upgrade of individual units in a controlled manner. The charm must support the
openstack-upgrade action, which in turn guarantees the availability of the
action-managed-upgrade option.
This method is slower than the all-in-one method due to the need for each unit to be upgraded separately. There is a lesser chance of downtime as the unit being upgraded must be in the process of servicing client requests for downtime to occur.
As a general rule, whenever there is the possibility of upgrading units individually, always upgrade the application leader first.
Note
The leader is the unit with a * next to it in the juju status output. It can also be discovered via the CLI:
juju run -a <application-name> is-leader
For example, to upgrade a three-unit glance application from Ussuri to Victoria
where glance/1 is the leader:
juju config glance action-managed-upgrade=True
juju config glance openstack-origin=cloud:focal-victoria
juju run-action --wait glance/1 openstack-upgrade
juju run-action --wait glance/0 openstack-upgrade
juju run-action --wait glance/2 openstack-upgrade
Paused-single-unit¶
The paused-single-unit method extends the single-unit method by allowing for
the upgrade of individual units while paused. Additional charm requirements are
the pause and resume actions.
This method provides more versatility by allowing a unit to be removed from service, upgraded, and returned to service. Each of these are distinct events whose timing is chosen by the operator.
This is the slowest method due to the need for each unit to be upgraded separately in addition to the required pause/resume management. However, it is the method that will result in the least downtime as clients will not be able to solicit a paused service.
For example, to upgrade a three-unit nova-compute application from Ussuri to
Victoria where nova-compute/0 is the leader:
juju config nova-compute action-managed-upgrade=True
juju config nova-compute openstack-origin=cloud:focal-victoria
juju run-action --wait nova-compute/0 pause
juju run-action --wait nova-compute/0 openstack-upgrade
juju run-action --wait nova-compute/0 resume
juju run-action --wait nova-compute/1 pause
juju run-action --wait nova-compute/1 openstack-upgrade
juju run-action --wait nova-compute/1 resume
juju run-action --wait nova-compute/2 pause
juju run-action --wait nova-compute/2 openstack-upgrade
juju run-action --wait nova-compute/2 resume
In addition, this method also permits a possible hacluster subordinate unit, which typically manages a VIP, to be paused so that client requests will never even be directed to the associated parent unit.
Attention
When there is an hacluster subordinate unit then it is recommended to always take advantage of the pause-single-unit method’s ability to pause it before upgrading the parent unit.
For example, to upgrade a three-unit keystone application from Ussuri to
Victoria where keystone/2 is the leader:
juju config keystone action-managed-upgrade=True
juju config keystone openstack-origin=cloud:focal-victoria
juju run-action --wait keystone-hacluster/1 pause
juju run-action --wait keystone/2 pause
juju run-action --wait keystone/2 openstack-upgrade
juju run-action --wait keystone/2 resume
juju run-action --wait keystone-hacluster/1 resume
juju run-action --wait keystone-hacluster/2 pause
juju run-action --wait keystone/1 pause
juju run-action --wait keystone/1 openstack-upgrade
juju run-action --wait keystone/1 resume
juju run-action --wait keystone-hacluster/2 resume
juju run-action --wait keystone-hacluster/0 pause
juju run-action --wait keystone/0 pause
juju run-action --wait keystone/0 openstack-upgrade
juju run-action --wait keystone/0 resume
juju run-action --wait keystone-hacluster/0 resume
Warning
The hacluster subordinate unit number may not necessarily match its parent
unit number. As in the above example, only for keystone/0 do the unit
numbers correspond (i.e. keystone-hacluster/0 is its subordinate unit).
Re-enable unattended-upgrades¶
In a previous step, unattended-upgrades were disabled on those cloud nodes that hosted multiple principal charms. Once such a node has had all of its services upgraded, unattended-upgrades should be re-enabled:
sudo dpkg-reconfigure -plow unattended-upgrades
Verify the new deployment¶
Check for errors in juju status output and any monitoring service.
Example upgrade¶
The OpenStack upgrade example page shows the explicit steps used to upgrade a basic cloud.
