Chapter 11. Upgrading the Compute node operating system

Procedure

1. 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:

     name: <ComputeRHEL8>
      description: |
       Basic Compute Node role
      CountDefault: 1
      rhsm_enforce_multios: 8.4
     ...
     ServicesDefault:
     ...
     - OS::TripleO::Services::NovaLibvirtLegacy

     Note

     Roles 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:

     name: <ComputeRHEL9>
      description: |
     Basic Compute Node role
      CountDefault: 1
     ...
     ServicesDefault:
     ...
     - OS::TripleO::Services::NovaLibvirt

     Note

     Roles that contain nodes being upgraded to RHEL 9.2 must include the NovaLibvirt service. Replace OS::TripleO::Services::NovaLibvirtLegacy with OS::TripleO::Services::NovaLibvirt.

   • Replace <ComputeRHEL9> with the name of your RHEL 9.2 role.

2. Copy the overcloud_upgrade_prepare.sh file to the copy_role_Compute_param.sh file:

   $ cp overcloud_upgrade_prepare.sh copy_role_Compute_param.sh

3. Edit the copy_role_Compute_param.sh file to include the copy_role_params.py script. This script generates the environment file that contains the additional parameters and resources for the new role. For example:

   /usr/share/openstack-tripleo-heat-templates/tools/copy_role_params.py --rolename-src <Compute_source_role> --rolename-dst <Compute_destination_role> \
    -o <Compute_new_role_params.yaml> \
   
   -e /home/stack/templates/internal.yaml \
   -e /usr/share/openstack-tripleo-heat-templates/environments/services/neutron-ovs.yaml \
   -e /home/stack/templates/network/network-environment.yaml \
   -e /home/stack/templates/inject-trust-anchor.yaml \
   -e /home/stack/templates/hostnames.yml \
   -e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/ceph-ansible.yaml \
   -e /home/stack/templates/nodes_data.yaml \
   -e /home/stack/templates/debug.yaml \
   -e /home/stack/templates/firstboot.yaml \
      -e /home/stack/overcloud-params.yaml \
    -e /home/stack/overcloud-deploy/overcloud/overcloud-network-environment.yaml \
   -e /home/stack/overcloud_adopt/baremetal-deployment.yaml \
   -e /home/stack/overcloud_adopt/generated-networks-deployed.yaml \
   -e /home/stack/overcloud_adopt/generated-vip-deployed.yaml \
   -e /usr/share/openstack-tripleo-heat-templates/environments/nova-hw-machine-type-upgrade.yaml \
   -e ~/containers-prepare-parameter.yaml

   • 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.

4. Run the copy_role_Compute_param.sh script:

   $ sh /home/stack/copy_role_Compute_param.sh

5. 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>

   Note

   This 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 the hostname_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 the count 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.

6. 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/overcloud_adopt/baremetal-deployment.yaml /home/stack/tripleo-<stack>-baremetal-deployment.yaml

   Note

   The output baremetal-deployment.yaml file is the same file that is used in the overcloud_upgrade_prepare.sh file during overcloud adoption.

7. 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 called ComputeRHEL8 that contains the nodes that are remaining on RHEL 8.4, COMPUTE_ROLES = --role ComputeRHEL8.

   python3
   /usr/share/openstack-tripleo-heat-templates/tools/multi-rhel-container-image-prepare.py \
       ${COMPUTE_ROLES} \
       --enable-multi-rhel \
       --excludes collectd \
       --excludes nova-libvirt \
       --minor-override "{${EL8_TAGS}${EL8_NAMESPACE}${CEPH_OVERRIDE}${NEUTRON_DRIVER}\"no_tag\":\"not_used\"}" \
       --major-override "{${EL9_TAGS}${NAMESPACE}${CEPH_OVERRIDE}${NEUTRON_DRIVER}\"no_tag\":\"not_used\"}" \
       --output-env-file \
       /home/stack/containers-prepare-parameter.yaml

8. Repeat this procedure to create additional roles and to move additional Compute nodes to those new roles.

Procedure

1. In the skip_rhel_release.yaml file, set the SkipRhelEnforcement parameter to false:

   parameter_defaults:
     SkipRhelEnforcement: false

2. Include the -e system_upgrade.yaml argument and the other required -e environment file arguments in the overcloud_upgrade_prepare.sh script as shown in the following example:

   $ openstack overcloud upgrade prepare --yes \
   ...
   -e /home/stack/system_upgrade.yaml  \
   -e /home/stack/<Compute_new_role_params.yaml> \
   ...

   • 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.
3. Optional: Migrate your instances. For more information on migration strategies, see Migrating virtual machines between Compute nodes and Preparing to migrate.
4. Run the overcloud_upgrade_prepare.sh script.

5. 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 the computerhel9-0, computerhel9-1, computerhel9-2, and computesriov-42 nodes from the ComputeRHEL9 and ComputeSRIOV roles.

   $ openstack overcloud upgrade run --yes --tags system_upgrade --stack <stack> --limit computerhel9-0,computerhel9-1,computerhel9-2,computesriov-42

   • Replace <stack> with the name of your stack.

6. 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 the computerhel9-0, computerhel9-1, computerhel9-2, and computesriov-42 nodes from the ComputeRHEL9 and ComputeSRIOV roles.

   $ openstack overcloud upgrade run --yes --stack <stack>  --limit computerhel9-0,computerhel9-1,computerhel9-2,computesriov-42