Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Fast Forward Upgrade: Updating Contrail Networking 1912.L4 and Red Hat OpenStack 13 to Contrail Networking 21.4.L2 and Red Hat Openstack 16.2

This document provides the steps needed to update an environment that is running Contrail Networking Release 1912.L4 and Red Hat OpenStack 13 to an environment running Contrail Networking 21.4.L2 and Red Hat Openstack 16.2.

The procedure provides a fast forward upgrade (FFU). AN FFU upgrades the Red Hat OpenStack software from it’s currently running version to a version that is several releases later. An FFU provides an opportunity to upgrade to OpenStack versions that are considered long life versions and upgrade when the next long life version is available. This document shows how to perform this FFU for Red Hat Openstack while also upgrading Contrail Networking.

When to Use This Procedure

The procedure in this document has been validated for the following Contrail Networking upgrade scenarios:

Table 1: Validated Upgrade Scenarios

Starting Releases

Target Releases

Contrail Networking Release 1912.L4Red Hat Openstack 13

Contrail Networking Release 21.4.L2Red Hat Openstack 16.2.4

Preparing for the Upgrade and Upgrading the Undercloud

This document will frequently reference the Red Hat Openstack document for performing the Red Hat Openstack upgrade. See Framework for Upgrades (13 to 16.2)

To upgrade the undercloud, see the Planning and preparation for an in-place upgrade through the Configuring the overcloud for a Leapp upgrade sections of the Framework for Upgrades (13 to 16.2) guide.

Upgrading the Overcloud

Before you begin, we strongly recommend becoming familiar with processes to efficiently upgrade the overcloud. See Speeding up an overcloud upgrade in the Framework for Upgrades (13 to 16.2) guide.

  1. (Only needed if undercloud is used as a container registry) Create a Contrail container file and upload the container file.
    1. Create a Contrail container file using the Heat template tools and import the existing registry files into the Contrail container file:

      Examples:

      To import the files from a password protected public registry:

      To import the files from a private secure registry:

      To import the files from a private insecure registry:

    2. From the undercloud, upload the container file:
  2. Clone the Tungsten Fabric deployment repository:
    Warning:

    Review the files in the Github repository at https://github.com/tungstenfabric/tf-deployment-test.git before entering this command to clone the files.

    In most scenarios, you will need to update some file parameters for your environment after cloning the repository.

    Note the following key directory locations in the repository for a Contrail Networking upgrade:

    • Tungsten fabric scripts location: tf-deployment-test/tree/master/rhosp/ffu_ziu_13_16/tf_specific

    • Red Hat-specific steps are available in this directory: tf-deployment-test/tree/master/rhosp/ffu_ziu_13_16/redhat_ffu_steps

  3. Prepare the templates to upgrade all of the overcloud nodes.

    Update the services.yaml file with the '21.4.L2' tag . Be aware of the following while performing this step:

    After entering this command, follow the instructions in Speeding up an overcloud upgrade to upgrade all overcloud nodes. All overcloud nodes should be upgraded in this step, including Openstack nodes, Contrail controller nodes, and compute nodes.

  4. For compute nodes, also perform these steps:
    1. Migrate the existing workloads. See the Migrating virtual machine instances between Compute nodes document from Red Hat.
    2. Be aware of the following potential problems and the workarounds if you run into them:

      • CEM-29946: A kernel upgrade fails during the compute node reboot. Containers are stuck in the creating state.

        Workaround: Reboot the node. After rebooting the node, add the following snippet to the ~/tripleo-heat-templates/upgrades-environment.yaml file:

        Note:

        This snippet assumes you are not using custom roles.

        If you are using custom roles, please replace Compute in line 2 of this snippet with your custom name.

      • CEM-29947: A compute node using DPDK fails during an FFU upgrade.

        Workaround: Add the following snippet to the ~/tripleo-heat-templates/upgrades-environment.yaml file:

        Note:

        This snippet assumes your are not using custom roles.

        If you are using custom roles, please replace ContrailDpdk in line 2 of this snippet with your custom name.

    3. Run the overcloud system upgrade prepare scripts.

      To obtain the scripts from Github, see the following URLs:

    4. Setup the vhost interfaces on the Contrail compute nodes by executing the playbook-nics-vhost0.yaml playbook.

    5. Upgrade the compute nodes in parallel:
      Warning:

      Execute these two commands as listed in this step. Do not execute a single command - for instance, openstack overcloud upgrade run --limit compute0 - as suggested in the Red Hat documentation to compute the compute node upgrade.

      Follow the steps in Upgrading Compute nodes in parallel to complete this step.

  5. Starting with the Synchronizing the overcloud stack step from the Framework for Upgrades (13 to 16.2) Red Hat document, complete the upgrade.