Appendix A. Deployment migration options

Prerequisites

1. Check the stores that are available through the Image service by using the glance stores-info command. In the following example, three stores are available: central, dcn1, and dcn2. These correspond to glance stores at the central location and edge sites, respectively:

     $ glance stores-info
     +----------+----------------------------------------------------------------------------------+
     | Property | Value                                                                            |
     +----------+----------------------------------------------------------------------------------+
     | stores   | [{"default": "true", "id": "central", "description": "central rbd glance         |
     |          | store"}, {"id": "dcn0", "description": "dcn0 rbd glance store"},                 |
     |          | {"id": "dcn1", "description": "dcn1 rbd glance store"}]                          |
     +----------+----------------------------------------------------------------------------------+

1. Add the desired subnets to undercloud.conf as shown in Configuring routed spine-leaf in the undercloud.
2. Re-run the undercloud installation command, openstack undercloud install.

3. Add the desired additional networks and roles to the overcloud templates, network_data.yaml and roles_data.yaml respectively.

   Note

   If you are using the {{network.name}}InterfaceRoutes parameter in the network configuration file, then you’ll need to ensure that the NetworkDeploymentActions parameter includes the value UPDATE.

     NetworkDeploymentActions: ['CREATE','UPDATE'])

4. Finally, re-run the overcloud installation script that includes all relevant heat templates for your cloud deployment.

Procedure

1. Create a backup of a volume in the first DCN site:

   $ cinder --os-volume-api-version 3.51 backup-create --name <volume_backup> --availability-zone <az_central> <edge_volume>

   • Replace <volume_backup> with a name for the volume backup.
   • Replace <az_central> with the name of the central availability zone that hosts the cinder-backup service.

   • Replace <edge_volume> with the name of the volume that you want to back up.

     Note

     If you experience issues with Ceph keyrings, you might need to restart the cinder-backup container so that the keyrings copy from the host to the container successfully.

2. Restore the backup to a new volume in the second DCN site:

   $ cinder --os-volume-api-version 3.51 create --availability-zone <az_2> --name <new_volume> --backup-id <volume_backup> <volume_size>

   • Replace <az_2> with the name of the availability zone where you want to restore the backup.
   • Replace <new_volume> with a name for the new volume.
   • Replace <volume_backup> with the name of the volume backup that you created in the previous step.
   • Replace <volume_size> with a value in GB equal to or greater than the size of the original volume.

Procedure

1. Log in to the undercloud host as the stack user.

2. Source the stackrc undercloud credentials file:

   $ source ~/stackrc

3. Verify that the following files that were exported during the undercloud upgrade contain the expected configuration for the overcloud upgrade. You can find the following files in the ~/overcloud-deploy directory:

   • tripleo-<stack>-passwords.yaml
   • tripleo-<stack>-network-data.yaml
   • tripleo-<stack>-virtual-ips.yaml

   • tripleo-<stack>-baremetal-deployment.yaml

     Note

     If the files were not generated after the undercloud upgrade, contact Red Hat Support.

     Important

     If you have a multi-cell environment, review Overcloud adoption for multi-cell environments for an example of copying the files to each cell stack.

4. On the main stack, copy the passwords.yaml file to the ~/overcloud-deploy/$(<stack>) directory. Repeat this step on each stack in your environment:

   $ cp ~/overcloud-deploy/<stack>/tripleo-<stack>-passwords.yaml ~/overcloud-deploy/<stack>/<stack>-passwords.yaml

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

5. If you are performing the preparation and adoption at the central location, copy the network-data.yaml file to the stack user’s home directory and deploy the networks. Do this only for the central location:

   $ cp /home/stack/overcloud-deploy/central/tripleo-central-network-data.yaml ~/
   $ mkdir /home/stack/overcloud_adopt
   $ openstack overcloud network provision --debug \
   --output /home/stack/overcloud_adopt/generated-networks-deployed.yaml tripleo-central-network-data.yaml

   For more information, see Provisioning and deploying your overcloud in Installing and managing Red Hat OpenStack Platform with director.

6. If you are performing the preparation and adoption at the central location, copy the virtual-ips.yaml file to the stack user’s home directory and provision the network VIPs. Do this only for the central location:

   $ cp /home/stack/overcloud-deploy/central/tripleo-central-virtual-ips.yaml ~/
   $ openstack overcloud network vip provision --debug \
   --stack <stack> --output \
   /home/stack/overcloud_adopt/generated-vip-deployed.yaml tripleo-central-virtual-ips.yaml

7. On the main stack, copy the baremetal-deployment.yaml file to the stack user’s home directory and provision the overcloud nodes. Repeat this step on each stack in your environment:

   $ cp ~/overcloud-deploy/<stack>/tripleo-<stack>-baremetal-deployment.yaml ~/
   $ openstack overcloud node provision --debug --stack <stack> \
   --output /home/stack/overcloud_adopt/baremetal-central-deployment.yaml \
   tripleo-<stack>-baremetal-deployment.yaml

   Note

   This is the final step of the overcloud adoption. If your overcloud adoption takes longer than 10 minutes to complete, contact Red Hat Support.

8. Complete the following steps to prepare the containers:

   1. Back up the containers-prepare-parameter.yaml file that you used for the undercloud upgrade:

      $ cp containers-prepare-parameter.yaml \
      containers-prepare-parameter.yaml.orig

   2. Define the following environment variables before you run the script to update the containers-prepare-parameter.yaml file:

      • NAMESPACE: The namespace for the UBI9 images. For example, NAMESPACE='"namespace":"example.redhat.com:5002",'
      • EL8_NAMESPACE: The namespace for the UBI8 images.
      • NEUTRON_DRIVER: The driver to use and determine which OpenStack Networking (neutron) container to use. Set to the type of containers you used to deploy the original stack. For example, set to NEUTRON_DRIVER='"neutron_driver":"ovn",' to use OVN-based containers.

      • EL8_TAGS: The tags of the UBI8 images, for example, EL8_TAGS='"tag":"17.1",'.

        • Replace "17.1", with the tag that you use in your content view.

      • EL9_TAGS: The tags of the UBI9 images, for example, EL9_TAGS='"tag":"17.1",'.

        • Replace "17.1", with the tag that you use in your content view.

          For more information about the tag parameter, see Container image preparation parameters in Customizing your Red Hat OpenStack Platform deployment.

      • CONTROL_PLANE_ROLES: The list of control plane roles using the --role option, for example, --role ControllerOpenstack, --role Database, --role Messaging, --role Networker, --role CephStorage. To view the list of control plane roles in your environment, run the following command:

        $ export STACK=<stack> \
        $ sudo awk '/tripleo_role_name/ {print "--role " $2}' \
        /var/lib/mistral/${STACK}/tripleo-ansible-inventory.yaml \
        | grep -vi compute

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

      • COMPUTE_ROLES: The list of Compute roles using the --role option, for example, --Compute-1. To view the list of Compute roles in your environment, run the following command:

        $ sudo awk '/tripleo_role_name/ {print "--role " $2}' \
        /var/lib/mistral/${STACK}/tripleo-ansible-inventory.yaml \
        | grep -i compute

      • CEPH_OVERRIDE: If you deployed Red Hat Ceph Storage, specify the Red Hat Ceph Storage 5 container images. For example:

        CEPH_OVERRIDE='"ceph_image":"rhceph-5-rhel8","ceph_tag":"<latest>",'

        • Replace <latest> with the latest ceph_tag version, for example, 5-499.

          The following is an example of the containers-prepare-parameter.yaml file configuration:

          NAMESPACE='"namespace":"registry.redhat.io/rhosp-rhel9",'
          EL8_NAMESPACE='"namespace":"registry.redhat.io/rhosp-rhel8",'
          NEUTRON_DRIVER='"neutron_driver":"ovn",'
          EL8_TAGS='"tag":"17.1",'
          EL9_TAGS='"tag":"17.1",'
          CONTROL_PLANE_ROLES="--role Controller"
          COMPUTE_ROLES="--role Compute"
          CEPH_TAGS='"ceph_tag":"5",'

   3. Run the following script to to update the containers-prepare-parameter.yaml file:

      Warning

      If you deployed Red Hat Ceph Storage, ensure that the CEPH_OVERRIDE environment variable is set to the correct values before executing the following command. Failure to do so results in issues when upgrading Red Hat Ceph Storage.

      $ python3 /usr/share/openstack-tripleo-heat-templates/tools/multi-rhel-container-image-prepare.py \
           ${COMPUTE_ROLES} \
           ${CONTROL_PLANE_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

      The multi-rhel-container-image-prepare.py script supports the following parameters:

      --output-env-file

      Writes the environment file that contains the default ContainerImagePrepare value.

      --local-push-destination

      Triggers an upload to a local registry.

      --enable-registry-login

      Enables the flag that allows the system to attempt to log in to a remote registry prior to pulling the containers. Use this flag when --local-push-destination is not used and the target systems have network connectivity to remote registries. Do not use this flag for an overcloud that might not have network connectivity to a remote registry.

      --enable-multi-rhel

      Enables multi-rhel.

      --excludes

      Lists the services to exclude.

      --major-override

      Lists the override parameters for a major release.

      --minor-override

      Lists the override parameters for a minor release.

      --role

      The list of roles.

      --role-file

      The role_data.yaml file.

   4. If you deployed Red Hat Ceph Storage, open the containers-prepare-parameter.yaml file to confirm that the Red Hat Ceph Storage 5 container images are specified and that there are no references to Red Hat Ceph Storage 6 container images.

9. If you have a director-deployed Red Hat Ceph Storage deployment, create a file called ceph_params.yaml and include the following content:

   parameter_defaults:
     CephSpecFqdn: true
     CephConfigPath: "/etc/ceph"
     CephAnsibleRepo: "rhceph-5-tools-for-rhel-8-x86_64-rpms"
     DeployedCeph: true

   Important

   Do not remove the ceph_params.yaml file after the RHOSP upgrade is complete. This file must be present in director-deployed Red Hat Ceph Storage environments. Additionally, any time you run openstack overcloud deploy, you must include the ceph_params.yaml file, for example, -e ceph_params.yaml.

   Note

   If your Red Hat Ceph Storage deployment includes short names, you must set the CephSpecFqdn parameter to false. If set to true, the inventory generates with both the short names and domain names, causing the Red Hat Ceph Storage upgrade to fail.

10. Create an environment file called upgrades-environment.yaml in your templates directory and include the following content:

    parameter_defaults:
      ExtraConfig:
        nova::workarounds::disable_compute_service_check_for_ffu: true
      DnsServers: ["<dns_servers>"]
      DockerInsecureRegistryAddress: <undercloud_FQDN>
      UpgradeInitCommand: |
        sudo subscription-manager repos --disable=*
          if $( grep -q  9.2  /etc/os-release )
          then
            sudo subscription-manager repos --enable=rhel-9-for-x86_64-baseos-eus-rpms --enable=rhel-9-for-x86_64-appstream-eus-rpms --enable=rhel-9-for-x86_64-highavailability-eus-rpms --enable=openstack-17.1-for-rhel-9-x86_64-rpms --enable=fast-datapath-for-rhel-9-x86_64-rpms
            sudo podman ps | grep -q ceph && subscription-manager repos --enable=rhceph-5-tools-for-rhel-9-x86_64-rpms
            sudo subscription-manager release --set=9.2
          else
            sudo subscription-manager repos --enable=rhel-8-for-x86_64-baseos-tus-rpms --enable=rhel-8-for-x86_64-appstream-tus-rpms --enable=rhel-8-for-x86_64-highavailability-tus-rpms --enable=openstack-17.1-for-rhel-8-x86_64-rpms --enable=fast-datapath-for-rhel-8-x86_64-rpms
            sudo podman ps | grep -q ceph && subscription-manager repos --enable=rhceph-5-tools-for-rhel-8-x86_64-rpms
            sudo subscription-manager release --set=8.4
          fi
    
          if $(sudo podman ps | grep -q ceph )
          then
            sudo dnf -y install cephadm
          fi

    • Replace <dns_servers> with a comma-separated list of your DNS server IP addresses, for example, ["10.0.0.36", "10.0.0.37"].

    • Replace <undercloud_FQDN> with the fully qualified domain name (FQDN) of the undercloud host, for example, "undercloud-0.ctlplane.redhat.local:8787".

      For more information about the upgrade parameters that you can configure in the environment file, see Upgrade parameters.

11. If you are performing the preparation and adoption at an edge location, set the AuthCloudName parameter to the name of the central location:

    parameter_defaults:
      AuthCloudName: central

12. If multiple Image service (glance) stores are deployed, set the Image service API policy for copy-image to allow all rules:

    parameter_defaults:
        GlanceApiPolicies: {glance-copy_image: {key 'copy-image', value: ""}}

13. On the undercloud, create a file called overcloud_upgrade_prepare.sh in your templates directory.

    • You must create this file for each stack in your environment. This file includes the original content of your overcloud deploy file and the environment files that are relevant to your environment.

    • If you are creating the overcloud_upgrade_prepare.sh for a DCN edge location, you must include the following templates:

      • An environment template that contains exported central site parameters. You can find this file in /home/stack/overcloud-deploy/centra/central-export.yaml.
      • generated-networks-deployed.yaml, the resulting file from running the openstack overcloud network provision command at the central location.

      • generated-vip-deployed.yaml, the resulting file from running the openstack overcloud network vip provision command at the central location. + For example:

        #!/bin/bash
        openstack overcloud upgrade prepare --yes \
          --timeout 460 \
          --templates /usr/share/openstack-tripleo-heat-templates \
          --ntp-server 192.168.24.1 \
          --stack <stack> \
          -r /home/stack/roles_data.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/templates/upgrades-environment.yaml \
          -e /home/stack/overcloud-params.yaml \
          -e /home/stack/overcloud-deploy/<stack>/overcloud-network-environment.yaml \
          -e /home/stack/overcloud-adopt/<stack>-passwords.yaml \
          -e /home/stack/overcloud_adopt/<stack>-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 /home/stack/skip_rhel_release.yaml \
          -e ~/containers-prepare-parameter.yaml

        Note

        If you have a multi-cell environment, review Overcloud adoption for multi-cell environments for an example of creating the overcloud_upgrade_prepare.sh file for each cell stack.

        1. In the original network-environment.yaml file (/home/stack/templates/network/network-environment.yaml), remove all the resource_registry resources that point to OS::TripleO::*::Net::SoftwareConfig.
        2. In the overcloud_upgrade_prepare.sh file, include the following options relevant to your environment:
      • The environment file (upgrades-environment.yaml) with the upgrade-specific parameters (-e).
      • The environment file (containers-prepare-parameter.yaml) with your new container image locations (-e). In most cases, this is the same environment file that the undercloud uses.
      • The environment file (skip_rhel_release.yaml) with the release parameters (-e).
      • Any custom configuration environment files (-e) relevant to your deployment.
      • If applicable, your custom roles (roles_data) file by using --roles-file.
      • For Ceph deployments, the environment file (ceph_params.yaml) with the Ceph parameters (-e).
      • The files that were generated during overcloud adoption (networks-deployed.yaml, vip-deployed.yaml,baremetal-deployment.yaml) (-e).
      • If applicable, the environment file (ipa-environment.yaml) with your IPA service (-e).

      • If you are using composable networks, the (network_data) file by using --network-file.

        Note

        Do not include the network-isolation.yaml file in your overcloud deploy file or the overcloud_upgrade_prepare.sh file. Network isolation is defined in the network_data.yaml file.

      • If you use a custom stack name, pass the name with the --stack option.

        Note

        You must include the nova-hw-machine-type-upgrade.yaml file in your templates until all of your RHEL 8 Compute nodes are upgraded to RHEL 9 in the environment. If this file is excluded, an error appears in the nova_compute.log in the /var/log/containers/nova directory. After you upgrade all of your RHEL 8 Compute nodes to RHEL 9, you can remove this file from your configuration and update the stack.

        1. In the director-deployed Red Hat Ceph Storage use case, if you enabled the Shared File Systems service (manila) with CephFS through NFS on the deployment that you are upgrading, you must specify an additional environment file at the end of the overcloud_upgrade_prepare.sh script file. You must add the environment file at the end of the script because it overrides another environment file that is specified earlier in the script:

           -e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/manila-cephfsganesha-config.yaml

        2. In the external Red Hat Ceph Storage use case, if you enabled the Shared File Systems service (manila) with CephFS through NFS on the deployment that you are upgrading, you must check that the associated environment file in the overcloud_upgrade_prepare.sh script points to the tripleo-based ceph-nfs role. If present, remove the following environment file:

           -e /usr/share/openstack-tripleo-heat-templates/environments/ceph-ansible/manila-cephfsganesha-config.yaml

           And add the following environment file:

           -e /usr/share/openstack-tripleo-heat-templates/environments/manila-cephfsganesha-config.yaml

14. Run the upgrade preparation script for each stack in your environment:

    $ source stackrc
    $ chmod 755 /home/stack/overcloud_upgrade_prepare.sh
    $ sh /home/stack/overcloud_upgrade_prepare.sh

    Note

    If you have a multi-cell environment, you must run the script for each overcloud_upgrade_prepare.sh file that you created for each cell stack. For an example, see Overcloud adoption for multi-cell environments.

15. Wait until the upgrade preparation completes.

16. Download the container images:

    $ openstack overcloud external-upgrade run --stack <stack> --tags container_image_prepare