Chapter 4. Updating the Overcloud

Procedure

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

2. Source the stackrc file:

   $ source ~/stackrc

3. To increase the number of concurrent processes that container-puppet uses to generate configuration files, you must configure the DockerPuppetProcessCount parameter.

   1. Create an environment file called updates-environment.yaml in your templates directory:

      $ touch ~/templates/updates-environment.yaml

   2. Edit the file and add the following content:

      parameter_defaults:
          DockerPuppetProcessCount: 8

   3. Use the -e option to include this environment file when you run the openstack overcloud update prepare, openstack overcloud ceph-upgrade run, and openstack overcloud update converge commands.

4. On a Controller node, archive your deleted database entries:

   1. From the overcloud, list all instances of the Controller nodes:

      $ source ~/overcloudrc
      $ openstack server list

   2. Log on to a Controller node that is running the nova_api_cron container:

      ssh heat-admin@<controller_ip>

      • Replace <controller name or IP> with the IP address of a Controller node.

   3. Archive deleted database entries:

      $ sudo docker exec -u 42436 -ti nova_api_cron bash
      $ nova-manage db archive_deleted_rows --max_rows 1000
      $ exit

5. To download all packages that are required for an update on all the overcloud nodes, complete the following steps:

   1. Create a static inventory file of your overcloud:

      $ tripleo-ansible-inventory \
      --ansible_ssh_user heat-admin \
      --static-yaml-inventory ~/inventory.yaml

   2. Create the following Ansible playbook:

      $ cat > ~/yum-download-only.yaml <<'EOF'
      - hosts: all
        gather_facts: false
        tasks:
          - name: Pre-download all packages on all overcloud nodes
            shell:
              yum upgrade -y --downloadonly
            become: true
      EOF

   3. Run the yum-download-only.yaml Ansible playbook:

      $ ansible-playbook \
      -i ~/inventory.yaml \
      -f 20 ~/yum-download-only.yaml \
      --limit Controller,Compute,CephStorage

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

2. Run the update preparation command:

   $ openstack overcloud update prepare \
       --templates \
       -r <ROLES DATA FILE> \
       -n <NETWORK DATA FILE> \
       -e /home/stack/templates/overcloud_images.yaml \
       -e /home/stack/templates/updates-environment.yaml \
       -e <ENVIRONMENT FILE> \
       -e <ENVIRONMENT FILE> \
       --stack <STACK_NAME>
       ...

   Include the following options relevant to your environment:

   • Custom configuration environment files (-e).
   • The environment file with your new container image locations (-e). Note that the update command might display a warning about using the --container-registry-file. You can ignore this warning as this option is deprecated in favor of using -e for the container image environment file.
   • 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.
   • 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.
3. Wait until the update preparation completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

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

   $ openstack overcloud ceph-upgrade run \
       --templates \
       -e <ENVIRONMENT FILE> \
       -e /home/stack/templates/overcloud_images.yaml \
       -e /home/stack/templates/updates-environment.yaml

   Include the following options relevant to your environment:

   • Custom configuration environment files (-e)
   • The environment file with your container image locations (-e). Note that the update command might display a warning about using the --container-registry-file. You can ignore this warning, as this option is deprecated in favor of using -e for the container image environment file.
   • If applicable, your custom roles (roles_data) file (--roles-file)
   • If applicable, your composable network (network_data) file (--networks-file)
3. Wait until the Ceph Storage node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

2. Run the update command:

   $ openstack overcloud update run --nodes Controller

3. Wait until the Controller node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

2. Run the update command:

   $ openstack overcloud update run --nodes Compute

3. Wait until the Compute node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

2. Run the update command:

   $ openstack overcloud update run --nodes ComputeHCI

3. Wait until the node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

2. Update group nodes.

   To update all nodes in a group:

   $ openstack overcloud update run --nodes <GROUP_NAME>

   To update a single node in a group:

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

   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, the command is:

   openstack overcloud update run --nodes CephStorage[0]

3. Wait until the node update completes.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

2. Run the update finalization command:

   $ openstack overcloud update converge \
       --templates \
       --stack <STACK_NAME> \
       -e /home/stack/templates/overcloud_images.yaml \
       -e /home/stack/templates/updates-environment.yaml \
       -e <ENVIRONMENT FILE>
       ...

   Include the following options relevant to your environment:

   • Custom configuration environment files (-e)
   • The environment file with your new container image locations (-e). Note that the update command might display a warning about using the --container-registry-file. You can ignore this warning as this option is deprecated in favor of using -e for the container image environment file.
   • If applicable, your custom roles (roles_data) file (--roles-file)
   • If applicable, your composable network (network_data) file (--networks-file)
   • If the name of your overcloud stack is different than the default name overcloud, you must include the --stack option in the update preparation command and replace <STACK_NAME> with the name of your overcloud stack.
3. Wait until the update finalization completes.