Upgrade OpenStack¶
Available since MOSK 21.5
This section provides instructions on how to upgrade the OpenStack version on a MOSK managed cluster.
Prerequisites¶
Verify that your OpenStack cloud is running on the latest MOSK release. See Release Compatibility Matrix for the release matrix and supported upgrade paths.
Just before the upgrade, back up your OpenStack databases. See Back up and restore a MariaDB Galera database for details.
Verify that OpenStack is healthy and operational. All OpenStack components in the
health
group in theOpenStackDeploymentStatus
CR should be in theReady
state. See OpenStackDeploymentStatus custom resource for details.Verify the workability of your OpenStack deployment by running Tempest against the OpenStack cluster as described in Run Tempest tests. Verification of the testing pass rate before upgrading will help you measure your cloud quality before and after upgrade.
Read carefully through the Release Notes of your MOSK version payingattention to the Known issues section and the OpenStack upstream release notes for the target OpenStack version.
Calculate the maintenance window using Calculate a maintenance window duration and notify users.
Perform the upgrade¶
To start the OpenStack upgrade, change the value of the
spec:openstack_version
parameter in the OpenStackDeployment
object
to the target OpenStack release.
Caution
It is not allowed to do skip level upgrades as well as downgrades.
When you change the value of the spec:openstack_version
parameter,
the OpenStack controller initializes the upgrade process.
To verify the upgrade status, use:
Logs from the
osdpl
container in the OpenStack controller pod.The
OpenStackDeploymentStatus
object.When upgrade starts, the
OPENSTACK VERSION
field content changes to the target OpenStack version, andSTATE
displaysAPPLYING
:kubectl -n openstack get osdplst NAME OPENSTACK VERSION CONTROLLER VERSION STATE osh-dev victoria 0.5.8.dev15 APPLYING
When upgrade finishes, the
STATE
field should displayAPPLIED
:kubectl -n openstack get osdplst NAME OPENSTACK VERSION CONTROLLER VERSION STATE osh-dev victoria 0.5.8.dev15 APPLIED
Verify the upgrade¶
Verify that OpenStack is healthy and operational. All OpenStack components in the
health
group in theOpenStackDeploymentStatus
CR should be in theReady
state. See OpenStackDeploymentStatus custom resource for details.Verify the workability of your OpenStack deployment by running Tempest against the OpenStack cluster as described in Run Tempest tests.