이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 14. Upgrading the Compute node operating system
You can upgrade the operating system on all of your Compute nodes to RHEL 9.2, or upgrade some Compute nodes while the rest remain on RHEL 8.4.
If your deployment includes hyperconverged infrastructure (HCI) nodes, you must upgrade all HCI nodes to RHEL 9. For more information about upgrading to RHEL 9, see Upgrading Compute nodes to RHEL 9.2.
For information about the duration and impact of this upgrade procedure, see Upgrade duration and impact.
Prerequisites
If you are using Red Hat Ceph Storage, before performing the Leapp upgrade verify if the ceph-common
package is present on your Compute nodes. If the ceph-common
package is present on a node, take the precautions described in Upgrading RHCS 5 hosts from RHEL 8 to RHEL 9 removes ceph-common package. Services fail to start. to ensure the Red Hat Ceph Storage services restart after the Compute node reboots after the Leapp upgrade.
14.1. Selecting Compute nodes for upgrade testing 링크 복사링크가 클립보드에 복사되었습니다!
The overcloud upgrade process allows you to either:
- Upgrade all nodes in a role.
- Upgrade individual nodes separately.
To ensure a smooth overcloud upgrade process, it is useful to test the upgrade on a few individual Compute nodes in your environment before upgrading all Compute nodes. This ensures no major issues occur during the upgrade while maintaining minimal downtime to your workloads.
Use the following recommendations to help choose test nodes for the upgrade:
- Select two or three Compute nodes for upgrade testing.
- Select nodes without any critical instances running.
If necessary, migrate critical instances from the selected test Compute nodes to other Compute nodes. Review which migration scenarios are supported:
Expand Source Compute node RHEL version Destination Compute node RHEL version Supported/Not supported RHEL 8
RHEL 8
Supported
RHEL 8
RHEL 9
Supported
RHEL 9
RHEL 9
Supported
RHEL 9
RHEL 8
Not supported
14.2. Upgrading all Compute nodes to RHEL 9.2 링크 복사링크가 클립보드에 복사되었습니다!
Upgrade all your Compute nodes to RHEL 9.2 to take advantage of the latest features and to reduce downtime.
Prerequisites
- If your deployment includes hyper-converged infrastructure (HCI) nodes, place hosts in maintenance mode to prepare the Red Hat Ceph Storage cluster on each HCI node for reboot. For more information, see Placing hosts in the maintenance mode using the Ceph Orchestrator in The Ceph Operations Guide.
If you are using RHOSP version 17.1.3 or earlier, before you run the system upgrade, ensure that no guests are running on the Compute hosts. Any guests that are running go into an error state. To avoid this issue, either live migrate your workloads or shut them down. For more information about live migration, see Live migrating an instance in Configuring the Compute service for instance creation.
Procedure
-
Log in to the undercloud host as the
stack
user. Source the
stackrc
undercloud credentials file:source ~/stackrc
$ source ~/stackrc
Copy to Clipboard Copied! Toggle word wrap Toggle overflow In the
container-image-prepare.yaml
file, ensure that only the tags specified in theContainerImagePrepare
parameter are included, and theMultiRhelRoleContainerImagePrepare
parameter is removed. For example:Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
In the
roles_data.yaml
file, replace theOS::TripleO::Services::NovaLibvirtLegacy
service with theOS::TripleO::Services::NovaLibvirt
service that is required for RHEL 9.2. Include the
-e
system_upgrade.yaml
argument and the other required-e
environment file arguments in theovercloud_upgrade_prepare.sh
script as shown in the following example:openstack overcloud upgrade prepare --yes
$ openstack overcloud upgrade prepare --yes … -e /home/stack/system_upgrade.yaml …
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Run the
overcloud_upgrade_prepare.sh
script. Upgrade the operating system on the Compute nodes to RHEL 9.2. Use the
--limit
option with a comma-separated list of nodes that you want to upgrade. The following example upgrades thecompute-0
,compute-1
, andcompute-2
nodes.openstack overcloud upgrade run --yes --tags system_upgrade --stack <stack> --limit compute-0,compute-1,compute-2
$ openstack overcloud upgrade run --yes --tags system_upgrade --stack <stack> --limit compute-0,compute-1,compute-2
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Replace
<stack>
with the name of your stack.
-
Replace
Upgrade the containers on the Compute nodes to RHEL 9.2. Use the
--limit
option with a comma-separated list of nodes that you want to upgrade. The following example upgrades thecompute-0
,compute-1
, andcompute-2
nodes.openstack overcloud upgrade run --yes --stack <stack> --limit compute-0,compute-1,compute-2
$ openstack overcloud upgrade run --yes --stack <stack> --limit compute-0,compute-1,compute-2
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
14.3. Upgrading Compute nodes to a Multi-RHEL environment 링크 복사링크가 클립보드에 복사되었습니다!
You can upgrade a portion of your Compute nodes to RHEL 9.2 while the rest of your Compute nodes remain on RHEL 8.4. This upgrade process involves the following fundamental steps:
-
Plan which nodes you want to upgrade to RHEL 9.2, and which nodes you want to remain on RHEL 8.4. Choose a role name for each role that you are creating for each batch of nodes, for example,
ComputeRHEL-9.2
andComputeRHEL-8.4
. Create roles that store the nodes that you want to upgrade to RHEL 9.2, or the nodes that you want to stay on RHEL 8.4. These roles can remain empty until you are ready to move your Compute nodes to a new role. You can create as many roles as you need and divide nodes among them any way you decide. For example:
-
If your environment uses a role called
ComputeSRIOV
and you need to run a canary test to upgrade to RHEL 9.2, you can create a newComputeSRIOVRHEL9
role and move the canary node to the new role. -
If your environment uses a role called
ComputeOffload
and you want to upgrade most nodes in that role to RHEL 9.2, but keep a few nodes on RHEL 8.4, you can create a newComputeOffloadRHEL8
role to store the RHEL 8.4 nodes. You can then select the nodes in the originalComputeOffload
role to upgrade to RHEL 9.2.
-
If your environment uses a role called
- Move the nodes from each Compute role to the new role.
Upgrade the operating system on specific Compute nodes to RHEL 9.2. You can upgrade nodes in batches from the same role or multiple roles.
NoteIn a Multi-RHEL environment, the deployment should continue to use the pc-i440fx machine type. Do not update the default to Q35. Migrating to the Q35 machine type is a separate, post-upgrade procedure to follow after all Compute nodes are upgraded to RHEL 9.2. For more information about migrating the Q35 machine type, see Updating the default machine type for hosts after an upgrade to RHOSP 17.
Use the following procedures to upgrade Compute nodes to a Multi-RHEL environment:
14.3.1. Creating roles for Multi-RHEL Compute nodes 링크 복사링크가 클립보드에 복사되었습니다!
Create new roles to store the nodes that you are upgrading to RHEL 9.2 or that are staying on RHEL 8.4, and move the nodes into the new roles.
Procedure
Create the relevant roles for your environment. In the
role_data.yaml
file, copy the source Compute role to use for the new role.Repeat this step for each additional role required. Roles can remain empty until you are ready to move your Compute nodes to the new roles.
If you are creating a RHEL 8 role:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteRoles that contain nodes remaining on RHEL 8.4 must include the
NovaLibvirtLegacy
service.-
Replace
<ComputeRHEL8>
with the name of your RHEL 8.4 role. If you are creating a RHEL 9 role:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteRoles that contain nodes being upgraded to RHEL 9.2 must include the
NovaLibvirt
service. ReplaceOS::TripleO::Services::NovaLibvirtLegacy
withOS::TripleO::Services::NovaLibvirt
.- Replace <ComputeRHEL9> with the name of your RHEL 9.2 role.
Copy the
overcloud_upgrade_prepare.sh
file to thecopy_role_Compute_param.sh
file:cp overcloud_upgrade_prepare.sh copy_role_Compute_param.sh
$ cp overcloud_upgrade_prepare.sh copy_role_Compute_param.sh
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Edit the
copy_role_Compute_param.sh
file to include thecopy_role_params.py
script. This script generates the environment file that contains the additional parameters and resources for the new role. For example:Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Replace
<Compute_source_role>
with the name of your source Compute role that you are copying. -
Replace
<Compute_destination_role>
with the name of your new role. -
Use the -o option to define the name of the output file that includes all the non-default values of the source Compute role for the new role. Replace
<Compute_new_role_params.yaml>
with the name of your output file.
-
Replace
Run the
copy_role_Compute_param.sh
script:sh /home/stack/copy_role_Compute_param.sh
$ sh /home/stack/copy_role_Compute_param.sh
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Move the Compute nodes from the source role to the new role:
python3 /usr/share/openstack-tripleo-heat-templates/tools/baremetal_transition.py --baremetal-deployment /home/stack/tripleo-<stack>-baremetal-deployment.yaml --src-role <Compute_source_role> --dst-role <Compute_destination_role> <Compute-0> <Compute-1> <Compute-2>
python3 /usr/share/openstack-tripleo-heat-templates/tools/baremetal_transition.py --baremetal-deployment /home/stack/tripleo-<stack>-baremetal-deployment.yaml --src-role <Compute_source_role> --dst-role <Compute_destination_role> <Compute-0> <Compute-1> <Compute-2>
Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteThis tool includes the original
/home/stack/tripleo-<stack>-baremetal-deployment.yaml
file that you exported during the undercloud upgrade. The tool copies and renames the source role definition in the/home/stack/tripleo-<stack>-baremetal-deployment.yaml
file. Then, it changes thehostname_format
to prevent a conflict with the newly created destination role. The tool then moves the node from the source role to the destination role and changes thecount
values.-
Replace
<stack>
with the name of your stack. -
Replace
<Compute_source_role>
with the name of the source Compute role that contains the nodes that you are moving to your new role. -
Replace
<Compute_destination_role>
with the name of your new role. -
Replace
<Compute-0>
<Compute-1>
<Compute-2>
with the names of the nodes that you are moving to your new role.
-
Replace
Reprovision the nodes to update the environment files in the stack with the new role location:
openstack overcloud node provision --stack <stack> --output /home/stack/templates/baremetal-deployment.yaml /home/stack/tripleo-<stack>-baremetal-deployment.yaml
$ openstack overcloud node provision --stack <stack> --output /home/stack/templates/baremetal-deployment.yaml /home/stack/tripleo-<stack>-baremetal-deployment.yaml
Copy to Clipboard Copied! Toggle word wrap Toggle overflow NoteThe output
baremetal-deployment.yaml
file is the same file that is used in theovercloud_upgrade_prepare.sh
file during overcloud adoption.Include any Compute roles that are remaining on RHEL 8.4 in the
COMPUTE_ROLES
parameter, and run the following script. For example, if you have a role calledComputeRHEL8
that contains the nodes that are remaining on RHEL 8.4,COMPUTE_ROLES = --role ComputeRHEL8
.Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Repeat this procedure to create additional roles and to move additional Compute nodes to those new roles.
14.3.2. Upgrading the Compute node operating system 링크 복사링크가 클립보드에 복사되었습니다!
Upgrade the operating system on selected Compute nodes to RHEL 9.2. You can upgrade multiple nodes from different roles at the same time.
Prerequisites
- Ensure that you have created the necessary roles for your environment. For more information about creating roles for a Multi-RHEL environment, see Creating roles for Multi-RHEL Compute nodes.
- If you plan to migrate your instances from your Compute nodes, review the supported migration scenarios. For more information, see Selecting Compute nodes for upgrade testing.
If you are using RHOSP version 17.1.3 or earlier, before you run the system upgrade, ensure that no guests are running on the Compute hosts. Any guests that are running go into an error state. To avoid this issue, either live migrate your workloads or shut them down. For more information about live migration, see Live migrating an instance in Configuring the Compute service for instance creation.
Procedure
In the
skip_rhel_release.yaml
file, set theSkipRhelEnforcement
parameter tofalse
:parameter_defaults: SkipRhelEnforcement: false
parameter_defaults: SkipRhelEnforcement: false
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Include the
-e
system_upgrade.yaml
argument and the other required-e
environment file arguments in theovercloud_upgrade_prepare.sh
script as shown in the following example:openstack overcloud upgrade prepare --yes \ ...
$ openstack overcloud upgrade prepare --yes \ ... -e /home/stack/system_upgrade.yaml \ -e /home/stack/<Compute_new_role_params.yaml> \ ...
Copy to Clipboard Copied! Toggle word wrap Toggle overflow -
Include the
system_upgrade.yaml
file with the upgrade-specific parameters (-e). -
Include the environment file that contains the parameters needed for the new role (-e). Replace
<Compute_new_role_params.yaml>
with the name of the environment file you created for your new role. - If you are upgrading nodes from multiple roles at the same time, include the environment file for each new role that you created.
-
Include the
- Optional: Migrate your instances. For more information on migration strategies, see Migrating virtual machines between Compute nodes and Preparing to migrate.
-
Run the
overcloud_upgrade_prepare.sh
script. Upgrade the operating system on specific Compute nodes. Use the
--limit
option with a comma-separated list of nodes that you want to upgrade. The following example upgrades thecomputerhel9-0
,computerhel9-1
,computerhel9-2
, andcomputesriov-42
nodes from theComputeRHEL9
andComputeSRIOV
roles.openstack overcloud upgrade run --yes --tags system_upgrade --stack <stack> --limit computerhel9-0,computerhel9-1,computerhel9-2,computesriov-42
$ openstack overcloud upgrade run --yes --tags system_upgrade --stack <stack> --limit computerhel9-0,computerhel9-1,computerhel9-2,computesriov-42
Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Replace <stack> with the name of your stack.
Upgrade the containers on the Compute nodes to RHEL 9.2. Use the
--limit
option with a comma-separated list of nodes that you want to upgrade. The following example upgrades thecomputerhel9-0
,computerhel9-1
,computerhel9-2
, andcomputesriov-42
nodes from theComputeRHEL9
andComputeSRIOV
roles.openstack overcloud upgrade run --yes --stack <stack> --limit computerhel9-0,computerhel9-1,computerhel9-2,computesriov-42
$ openstack overcloud upgrade run --yes --stack <stack> --limit computerhel9-0,computerhel9-1,computerhel9-2,computesriov-42
Copy to Clipboard Copied! Toggle word wrap Toggle overflow