Chapter 4. Updating the overcloud

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the update preparation command:

   $ openstack overcloud update prepare \
       --templates \
       --stack <stack_name> \
       -r <roles_data_file> \
       -n <network_data_file> \
       -e <environment_file> \
       -e <environment_file> \
       …​

   Copy to Clipboard Toggle word wrap

   Include the following options relevant to your environment:

   • If the name of your overcloud stack is different to the default name overcloud, include the --stack option in the update preparation command and replace <stack_name> with the name of your stack.
   • If you use your own custom roles, include your custom roles (<roles_data>) file (-r).
   • If you use custom networks, include your composable network (_<network_data>) file _ (-n).
   • If you deploy a high availability cluster, include the --ntp-server option in the update preparation command, or include the NtpServer parameter and value in your environment file.
   • Any custom configuration environment files (-e).
3. Wait until the update preparation completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the openstack overcloud external-update run command against tasks tagged with the container_image_prepare tag:

   $ openstack overcloud external-update run --stack <stack_name> --tags container_image_prepare

   Copy to Clipboard Toggle word wrap

Procedure

1. Log into the undercloud as the stack user.

2. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

3. Run the openstack overcloud external-update run command against the tasks that have the ovn tag:

   $ openstack overcloud external-update run --stack <stack_name> --tags ovn

   Copy to Clipboard Toggle word wrap
4. Wait until the ovn-controller container update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the update command:

   $ openstack overcloud update run --stack <stack_name> --limit Controller

   Copy to Clipboard Toggle word wrap
3. Wait until the Controller node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the update command:

   $ openstack overcloud update run --stack <stack_name> --limit Compute

   Copy to Clipboard Toggle word wrap
3. Wait until the Compute node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the update command:

   $ openstack overcloud update run --stack <stack_name> --limit ComputeHCI

   Copy to Clipboard Toggle word wrap
3. Wait until the node update completes.

4. Run the Ceph Storage update command. For example:

   $ openstack overcloud external-update run --stack <stack_name> --tags ceph

   Copy to Clipboard Toggle word wrap
5. Wait until the Compute HCI node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Update group nodes.

   To update all nodes in a group:

   $ openstack overcloud update run --limit <GROUP_NAME>

   Copy to Clipboard Toggle word wrap

   To update a single node in a group:

   $ openstack overcloud update run --limit <GROUP_NAME> [NODE_INDEX]

   Copy to Clipboard Toggle word wrap
   Note

   Ensure that you update all nodes if you choose to update nodes individually.

   The index of the first node in a group is zero (0). For example, to update the first node in a group named CephStorage:

   openstack overcloud update run --limit CephStorage[0]

3. Wait until the node update completes.

4. Run the Ceph Storage container update command:

   $ openstack overcloud external-update run --tags ceph

   Copy to Clipboard Toggle word wrap
5. Wait until the Ceph Storage container update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Run the openstack overcloud external-update run command against tasks that use the online_upgrade tag:

   $ openstack overcloud external-update run --tags online_upgrade

   Copy to Clipboard Toggle word wrap

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap
2. To re-enable fencing in your overcloud, in the fencing.yaml environment file, set the EnableFencing parameter to true.

3. Run the update finalization command:

   $ openstack overcloud update converge \
       --templates \
       --stack <stack_name> \
       -r <roles_data_file> \
       -n <network_data_file> \
       -e <environment_file> \
       -e <environment_file> \
       ...
       ...

   Copy to Clipboard Toggle word wrap

   Include the following options relevant to your environment:

   • The fencing.yaml environment file, with the EnableFencing parameter set to true.
   • If the name of your overcloud stack is different to the default name overcloud, include the --stack option in the update preparation command and replace <stack_name> with the name of your stack.
   • If using your own custom roles, include your custom roles (<roles_data>) file (-r)
   • If using custom networks, include your composable network (<network_data>) file (-n)
   • Any custom configuration environment files (-e).
4. Wait until the update finalization completes.