Red Hat Training
A Red Hat training course is available for Red Hat OpenStack Platform
Chapter 3. Upgrading the Undercloud
This process upgrades the undercloud and its overcloud images to Red Hat OpenStack Platform 13.
3.1. Upgrading the undercloud to OpenStack Platform 13
This procedure upgrades the undercloud toolset and the core Heat template collection to the OpenStack Platform 13 release.
Procedure
-
Log in to director as the
stack
user. Disable the current OpenStack Platform repository:
$ sudo subscription-manager repos --disable=rhel-7-server-openstack-12-rpms
Set the RHEL version to RHEL 7.9:
$ sudo subscription-manager release --set=7.9
Enable the new OpenStack Platform repository:
$ sudo subscription-manager repos --enable=rhel-7-server-openstack-13-rpms
Re-enable updates to the overcloud base images:
$ sudo yum-config-manager --setopt=exclude= --save
Run
yum
to upgrade the director’s main packages:$ sudo yum update -y python-tripleoclient
Run the following command to upgrade the undercloud:
$ openstack undercloud upgrade
- Wait until the undercloud upgrade process completes.
Reboot the undercloud to update the operating system’s kernel and other system packages:
$ sudo reboot
- Wait until the node boots.
You have upgraded the undercloud to the OpenStack Platform 13 release.
3.2. Upgrading the overcloud images
You need to replace your current overcloud images with new versions. The new images ensure the director can introspect and provision your nodes using the latest version of OpenStack Platform software.
Prerequisites
- You have upgraded the undercloud to the latest version.
Procedure
Source the undercloud access details:
$ source ~/stackrc
Remove any existing images from the
images
directory on thestack
user’s home (/home/stack/images
):$ rm -rf ~/images/*
Extract the archives:
$ cd ~/images $ for i in /usr/share/rhosp-director-images/overcloud-full-latest-13.0.tar /usr/share/rhosp-director-images/ironic-python-agent-latest-13.0.tar; do tar -xvf $i; done $ cd ~
Import the latest images into the director:
$ openstack overcloud image upload --update-existing --image-path /home/stack/images/
Configure your nodes to use the new images:
$ openstack overcloud node configure $(openstack baremetal node list -c UUID -f value)
Verify the existence of the new images:
$ openstack image list $ ls -l /httpboot
When deploying overcloud nodes, ensure the overcloud image version corresponds to the respective heat template version. For example, only use the OpenStack Platform 13 images with the OpenStack Platform 13 heat templates.
The new overcloud-full
image replaces the old overcloud-full
image. If you made changes to the old image, you must repeat the changes in the new image, especially if you want to deploy new nodes in the future.
3.3. Comparing Previous Template Versions
The upgrade process installs a new set of core Heat templates that correspond to the latest overcloud version. Red Hat OpenStack Platform’s repository retains the previous version of the core template collection in the openstack-tripleo-heat-templates-compat
package. This procedure shows how to compare these versions so you can identify changes that might affect your overcloud upgrade.
Procedure
Install the
openstack-tripleo-heat-templates-compat
package:$ sudo yum install openstack-tripleo-heat-templates-compat
This installs the previous templates in the
compat
directory of your Heat template collection (/usr/share/openstack-tripleo-heat-templates/compat
) and also creates a link tocompat
named after the previous version (pike
). These templates are backwards compatible with the upgraded director, which means you can use the latest version of the director to install an overcloud of the previous version.Create a temporary copy of the core Heat templates:
$ cp -a /usr/share/openstack-tripleo-heat-templates /tmp/osp13
Move the previous version into its own directory:
$ mv /tmp/osp13/compat /tmp/osp12
Perform a
diff
on the contents of both directories:$ diff -urN /tmp/osp12 /tmp/osp13
This shows the core template changes from one version to the next. These changes provide an idea of what should occur during the overcloud upgrade.
3.4. Undercloud Post-Upgrade Notes
-
If using a local set of core templates in your
stack
users home directory, ensure you update the templates using the recommended workflow in "Using Customized Core Heat Templates". You must update the local copy before upgrading the overcloud.
3.5. Next Steps
The undercloud upgrade is complete. You can now prepare the overcloud for the upgrade.