Procedure

1. Run the openstack overcloud deploy command and include:

   • All options and custom environment files relevant to your environment, such as network isolation and storage.
   • The overcloud_images.yaml environment file generated in Section 4.2, “Preparing for Containerized Services”.

   • The major-upgrade-composable-steps-docker.yaml environment file.

     For example:

   $ openstack overcloud deploy --templates \
     -e /home.stack/templates/node_count.yaml \
     -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
     -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml \
     -e /home/stack/templates/network_environment.yaml \
     -e /home/stack/templates/overcloud_images.yaml  \
     -e /usr/share/openstack-tripleo-heat-templates/environments/major-upgrade-composable-steps-docker.yaml \
     --ntp-server pool.ntp.org

2. Wait until the overcloud updates with the new environment file’s configuration.

   Important

   The upgrade disables the OpenStack Networking (neutron) server and L3 Agent. This means you cannot create new routers during this step. You can still access instances during this period.

3. Check if all services are active. For example, to check services on a Controllor node:

   [stack@director ~]$ ssh heat-admin@192.168.24.10
   [heat-admin@overcloud-controller-0 ~]$ sudo pcs status
   [heat-admin@overcloud-controller-0 ~]$ sudo docker ps

Procedure

1. Obtain a list of Object Storage nodes:

   $ openstack server list -c Name -f value --name objectstorage

2. Perform the following steps for each Object Storage node in the list:

   1. Run the upgrade-non-controller.sh script using the node name to identify the node to upgrade:

      $ upgrade-non-controller.sh --upgrade overcloud-objectstorage-0

      Note

      If using pre-provisioned node infrastructure, see Section 4.9, “Preparing for Pre-Provisioned Nodes Upgrade” for changes with this command.

   2. Wait until the Object Storage node completes the upgrade.

   3. Reboot the Object Storage node:

      $ openstack server reboot overcloud-objectstorage-0

   4. Wait until the Object Storage node completes the reboot.

1. Select a Compute node to upgrade
2. Migrate instances to another Compute node
3. Upgrade the empty Compute node
4. Reboot and enable the upgraded Compute node

1. List all Compute nodes:

   $ source ~/stackrc
   $ openstack server list -c Name -f value --name compute

2. Select a Compute node to upgrade and note its UUID and name.

1. From the undercloud, select a Compute Node to reboot and disable it:

   $ source ~/overcloudrc
   (overcloud) $ openstack compute service list
   (overcloud) $ openstack compute service set [hostname] nova-compute --disable

2. List all instances on the Compute node:

   (overcloud) $ openstack server list --host [hostname] --all-projects

3. Use one of the following commands to migrate your instances:

   1. Migrate the instance to a specific host of your choice:

      (overcloud) $ openstack server migrate [instance-id] --live [target-host]--wait

   2. Let nova-scheduler automatically select the target host:

      (overcloud) $ nova live-migration [instance-id]

   3. Live migrate all instances at once:

      $ nova host-evacuate-live [hostname]

      Note

      The nova command might cause some deprecation warnings, which are safe to ignore.

4. Wait until migration completes.

5. Confirm the migration was successful:

   (overcloud) $ openstack server list --host [hostname] --all-projects

6. Continue migrating instances until none remain on the chosen Compute Node.

1. Run the upgrade-non-controller.sh script using the node name to identify the node to upgrade:

   $ upgrade-non-controller.sh --upgrade overcloud-compute-0

   Note

   If using pre-provisioned node infrastructure, see Section 4.9, “Preparing for Pre-Provisioned Nodes Upgrade” for changes with this command.

2. Wait until the Compute node completes the upgrade.

1. Log into the Compute Node and reboot it:

   [heat-admin@overcloud-compute-0 ~]$ sudo reboot

2. Wait until the node boots.

3. Enable the Compute Node again:

   $ source ~/overcloudrc
   (overcloud) $ openstack compute service set [hostname] nova-compute --enable

4. Check whether the Compute node is enabled:

   (overcloud) $ openstack compute service list

Procedure

1. Run the openstack overcloud deploy command and include:

   • All options and custom environment files relevant to your environment, such as network isolation and storage.
   • The overcloud_images.yaml environment file generated in Section 4.2, “Preparing for Containerized Services”.

   • The major-upgrade-converge-docker.yaml environment file.

     For example:

   $ openstack overcloud deploy --templates \
     -e /home.stack/templates/node_count.yaml \
     -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
     -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml \
     -e /home/stack/templates/network_environment.yaml \
     -e /home/stack/templates/overcloud_images.yaml  \
     -e /usr/share/openstack-tripleo-heat-templates/environments/major-upgrade-converge-docker.yaml \
     --ntp-server pool.ntp.org

2. Wait until the overcloud updates with the new environment file’s configuration.

3. Check if all services are active. For example, to check services on a Controllor node:

   [stack@director ~]$ ssh heat-admin@192.168.24.10
   [heat-admin@overcloud-controller-0 ~]$ sudo pcs status
   [heat-admin@overcloud-controller-0 ~]$ sudo systemctl list-units 'openstack-*' 'neutron-*' 'httpd*'