Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 6. Non-Director Environments: Upgrading Individual OpenStack Services (Live Compute) in a High Availability Environment

This chapter describes the steps you should follow to upgrade your cloud deployment by updating one service at a time with live compute in a High Availability (HA) environment. This scenario upgrades from Red Hat OpenStack Platform 9 to Red Hat OpenStack Platform 10 in environments that do not use the director.

A live Compute upgrade minimizes interruptions to your Compute service, with only a few minutes for the smaller services, and a longer migration interval for the workloads moving to newly-upgraded Compute hosts. Existing workloads can run indefinitely, and you do not need to wait for a database migration.

Important

Due to certain package dependencies, upgrading the packages for one OpenStack service might cause Python libraries to upgrade before other OpenStack services upgrade. This might cause certain services to fail prematurely. In this situation, continue upgrading the remaining services. All services should be operational upon completion of this scenario.

Note

This method may require additional hardware resources to bring up the Compute nodes.

Note

The procedures in this chapter follow the architectural naming convention followed by all Red Hat OpenStack Platform documentation. If you are unfamiliar with this convention, refer to Architecture Guide available at Red Hat OpenStack Platform Documentation Suite before proceeding.

6.1. Pre-Upgrade Tasks
Copy link

On each node, change to the Red Hat OpenStack Platform 10 repository using the subscription-manager command: 

# subscription-manager repos --disable=rhel-7-server-openstack-9-rpms
# subscription-manager repos --enable=rhel-7-server-openstack-10-rpms
Copy to Clipboard Toggle word wrap

Upgrade the openstack-selinux package: 

# yum upgrade openstack-selinux
Copy to Clipboard Toggle word wrap

This is necessary to ensure that the upgraded services will run correctly on a system with SELinux enabled.

6.2. Upgrading MariaDB
Copy link

Perform the follow steps on each host running MariaDB. Complete the steps on one host before starting the process on another host.

  1. Stop the service from running on the local node: 

    # pcs resource ban galera-master $(crm_node -n)
    Copy to Clipboard Toggle word wrap

  2. Wait until pcs status shows that the service is no longer running on the local node. This may take a few minutes. The local node transitions to slave mode: 

    Master/Slave Set: galera-master [galera]
Masters: [ overcloud-controller-1 overcloud-controller-2 ]
Slaves: [ overcloud-controller-0 ]
    Copy to Clipboard Toggle word wrap

    The node eventually transitions to stopped: 

    Master/Slave Set: galera-master [galera]
Masters: [ overcloud-controller-1 overcloud-controller-2 ]
Stopped: [ overcloud-controller-0 ]
    Copy to Clipboard Toggle word wrap

  3. Upgrade the relevant packages: 

    # yum upgrade '*mariadb*' '*galera*'
    Copy to Clipboard Toggle word wrap

  4. Allow Pacemaker to schedule the galera resource on the local node: 

    # pcs resource clear galera-master
    Copy to Clipboard Toggle word wrap

  5. Wait until pcs status shows that the galera resource is running on the local node as a master. The pcs status command should provide output similar to the following: 

    Master/Slave Set: galera-master [galera]
Masters: [ overcloud-controller-0 overcloud-controller-1 overcloud-controller-2 ]
    Copy to Clipboard Toggle word wrap

Perform this procedure on each node individually until the MariaDB cluster completes a full upgrade.

6.3. Upgrading MongoDB
Copy link

This procedure upgrades MongoDB, which acts as the backend database for the OpenStack Telemetry service.

  1. Remove the mongod resource from Pacemaker’s control: 

    # pcs resource unmanage mongod-clone
    Copy to Clipboard Toggle word wrap

  2. Stop the service on all Controller nodes. On each Controller node, run the following: 

    # systemctl stop mongod
    Copy to Clipboard Toggle word wrap

  3. Upgrade the relevant packages: 

    # yum upgrade 'mongodb*' 'python-pymongo*'
    Copy to Clipboard Toggle word wrap

  4. Reload systemd to account for updated unit files: 

    # systemctl daemon-reload
    Copy to Clipboard Toggle word wrap

  5. Restart the mongod service on your controllers by running, on each controller: 

    # systemctl start mongod
    Copy to Clipboard Toggle word wrap

  6. Clean up the resource: 

    # pcs resource cleanup mongod-clone
    Copy to Clipboard Toggle word wrap

  7. Return the resource to Pacemaker control: 

    # pcs resource manage mongod-clone
    Copy to Clipboard Toggle word wrap
  8. Wait until the output of pcs status shows that the above resources are running.

6.4. Upgrading WSGI Services
Copy link

This procedure upgrades the packages for the WSGI services on all Controller nodes simultaneously. This includes OpenStack Identity (keystone) and OpenStack Dashboard (horizon).

  1. Remove the service from Pacemaker’s control: 

    # pcs resource unmanage httpd-clone
    Copy to Clipboard Toggle word wrap

  2. Stop the httpd service by running the following on each Controller node: 

    # systemctl stop httpd
    Copy to Clipboard Toggle word wrap

  3. Upgrade the relevant packages: 

    # yum -d1 -y upgrade \*keystone\*
# yum -y upgrade \*horizon\* \*openstack-dashboard\* httpd
# yum -d1 -y upgrade \*horizon\* \*python-django\*
    Copy to Clipboard Toggle word wrap

  4. Reload systemd to account for updated unit files on each Controller node: 

    # systemctl daemon-reload
    Copy to Clipboard Toggle word wrap

  5. Earlier versions of the installer may not have configured your system to automatically purge expired Keystone token, it is possible that your token table has a large number of expired entries. This can dramatically increase the time it takes to complete the database schema upgrade.

    Flush expired tokens from the database to alleviate the problem. Run the keystone-manage command before running the Identity database upgrade. 

    # keystone-manage token_flush
    Copy to Clipboard Toggle word wrap

    This flushes expired tokens from the database. You can arrange to run this command periodically (e.g., daily) using cron.

  6. Update the Identity service database schema: 

    # su -s /bin/sh -c "keystone-manage db_sync" keystone
    Copy to Clipboard Toggle word wrap

  7. Restart the service by running the following on each Controller node: 

    # systemctl start httpd
    Copy to Clipboard Toggle word wrap

  8. Clean up the Identity service using Pacemaker: 

    # pcs resource cleanup httpd-clone
    Copy to Clipboard Toggle word wrap

  9. Return the resource to Pacemaker control: 

    # pcs resource manage httpd-clone
    Copy to Clipboard Toggle word wrap
  10. Wait until the output of pcs status shows that the above resources are running.

6.5. Upgrading Image service (glance)
Copy link

This procedure upgrades the packages for the Image service on all Controller nodes simultaneously.

  1. Stop the Image service resources in Pacemaker: 

    # pcs resource disable openstack-glance-registry-clone
# pcs resource disable openstack-glance-api-clone
    Copy to Clipboard Toggle word wrap
  2. Wait until the output of pcs status shows that both services have stopped running.

  3. Upgrade the relevant packages: 

    # yum upgrade '*glance*'
    Copy to Clipboard Toggle word wrap

  4. Reload systemd to account for updated unit files: 

    # systemctl daemon-reload
    Copy to Clipboard Toggle word wrap

  5. Update the Image service database schema: 

    # su -s /bin/sh -c "glance-manage db_sync" glance
    Copy to Clipboard Toggle word wrap

  6. Clean up the Image service using Pacemaker: 

    # pcs resource cleanup openstack-glance-api-clone
# pcs resource cleanup openstack-glance-registry-clone
    Copy to Clipboard Toggle word wrap

  7. Restart Image service resources in Pacemaker: 

    # pcs resource enable openstack-glance-api-clone
# pcs resource enable openstack-glance-registry-clone
    Copy to Clipboard Toggle word wrap
  8. Wait until the output of pcs status shows that the above resources are running.

6.6. Upgrading Block Storage service (cinder)
Copy link

This procedure upgrades the packages for the Block Storage service on all Controller nodes simultaneously.

  1. Stop all Block Storage service resources in Pacemaker: 

    # pcs resource disable openstack-cinder-api-clone
# pcs resource disable openstack-cinder-scheduler-clone
# pcs resource disable openstack-cinder-volume
    Copy to Clipboard Toggle word wrap
  2. Wait until the output of pcs status shows that the above services have stopped running.

  3. Upgrade the relevant packages: 

    # yum upgrade '*cinder*'
    Copy to Clipboard Toggle word wrap

  4. Reload systemd to account for updated unit files: 

    # systemctl daemon-reload
    Copy to Clipboard Toggle word wrap

  5. Update the Block Storage service database schema: 

    # su -s /bin/sh -c "cinder-manage db sync" cinder
    Copy to Clipboard Toggle word wrap

  6. Clean up the Block Storage service using Pacemaker: 

    # pcs resource cleanup openstack-cinder-volume
# pcs resource cleanup openstack-cinder-scheduler-clone
# pcs resource cleanup openstack-cinder-api-clone
    Copy to Clipboard Toggle word wrap

  7. Restart all Block Storage service resources in Pacemaker: 

    # pcs resource enable openstack-cinder-volume
# pcs resource enable openstack-cinder-scheduler-clone
# pcs resource enable openstack-cinder-api-clone
    Copy to Clipboard Toggle word wrap
  8. Wait until the output of pcs status shows that the above resources are running.

6.7. Upgrading Orchestration (heat)
Copy link

This procedure upgrades the packages for the Orchestration service on all Controller nodes simultaneously.

  1. Stop Orchestration resources in Pacemaker: 

    # pcs resource disable openstack-heat-api-clone
# pcs resource disable openstack-heat-api-cfn-clone
# pcs resource disable openstack-heat-api-cloudwatch-clone
# pcs resource disable openstack-heat-engine-clone
    Copy to Clipboard Toggle word wrap
  2. Wait until the output of pcs status shows that the above services have stopped running.

  3. Upgrade the relevant packages: 

    # yum upgrade '*heat*'
    Copy to Clipboard Toggle word wrap

  4. Reload systemd to account for updated unit files: 

    # systemctl daemon-reload
    Copy to Clipboard Toggle word wrap

  5. Update the Orchestration database schema: 

    # su -s /bin/sh -c "heat-manage db_sync" heat
    Copy to Clipboard Toggle word wrap

  6. Clean up the Orchestration service using Pacemaker: 

    # pcs resource cleanup openstack-heat-clone
# pcs resource cleanup openstack-heat-api-cloudwatch-clone
# pcs resource cleanup openstack-heat-api-cfn-clone
# pcs resource cleanup openstack-heat-api-clone
    Copy to Clipboard Toggle word wrap

  7. Restart Orchestration resources in Pacemaker: 

    # pcs resource enable openstack-heat-clone
# pcs resource enable openstack-heat-api-cloudwatch-clone
# pcs resource enable openstack-heat-api-cfn-clone
# pcs resource enable openstack-heat-api-clone
    Copy to Clipboard Toggle word wrap
  8. Wait until the output of pcs status shows that the above resources are running.

6.8. Upgrading Telemetry (ceilometer)
Copy link

This procedure upgrades the packages for the Telemetry service on all Controller nodes simultaneously.

Note

This component has some additional upgrade procedures detailed in Chapter 7, Additional Procedures for Non-Director Environments. These additional procedures are optional for manual environments but help align with the current OpenStack Platform recommendations.

  1. Stop all Telemetry resources in Pacemaker: 

    # pcs resource disable openstack-ceilometer-api-clone
# pcs resource disable openstack-ceilometer-collector-clone
# pcs resource disable openstack-ceilometer-notification-clone
# pcs resource disable openstack-ceilometer-central-clone
# pcs resource disable openstack-aodh-evaluator-clone
# pcs resource disable openstack-aodh-listener-clone
# pcs resource disable openstack-aodh-notifier-clone
# pcs resource disable openstack-gnocchi-metricd-clone
# pcs resource disable openstack-gnocchi-statsd-clone
# pcs resource disable delay-clone
    Copy to Clipboard Toggle word wrap
  2. Wait until the output of pcs status shows that the above services have stopped running.

  3. Upgrade the relevant packages: 

    # yum upgrade '*ceilometer*' '*aodh*' '*gnocchi*'
    Copy to Clipboard Toggle word wrap

  4. Reload systemd to account for updated unit files: 

    # systemctl daemon-reload
    Copy to Clipboard Toggle word wrap

  5. Use the following command to update Telemetry database schema. 

    # ceilometer-dbsync
# aodh-dbsync
# gnocchi-upgrade
    Copy to Clipboard Toggle word wrap

  6. Clean up the Telemetry service using Pacemaker: 

    # pcs resource cleanup delay-clone
# pcs resource cleanup openstack-ceilometer-api-clone
# pcs resource cleanup openstack-ceilometer-collector-clone
# pcs resource cleanup openstack-ceilometer-notification-clone
# pcs resource cleanup openstack-ceilometer-central-clone
# pcs resource cleanup openstack-aodh-evaluator-clone
# pcs resource cleanup openstack-aodh-listener-clone
# pcs resource cleanup openstack-aodh-notifier-clone
# pcs resource cleanup openstack-gnocchi-metricd-clone
# pcs resource cleanup openstack-gnocchi-statsd-clone
    Copy to Clipboard Toggle word wrap

  7. Restart all Telemetry resources in Pacemaker: 

    # pcs resource enable delay-clone
# pcs resource enable openstack-ceilometer-api-clone
# pcs resource enable openstack-ceilometer-collector-clone
# pcs resource enable openstack-ceilometer-notification-clone
# pcs resource enable openstack-ceilometer-central-clone
# pcs resource enable openstack-aodh-evaluator-clone
# pcs resource enable openstack-aodh-listener-clone
# pcs resource enable openstack-aodh-notifier-clone
# pcs resource enable openstack-gnocchi-metricd-clone
# pcs resource enable openstack-gnocchi-statsd-clone
    Copy to Clipboard Toggle word wrap
  8. Wait until the output of pcs status shows that the above resources are running.
Important

Previous versions of the Telemetry service used an value for the rpc_backend parameter that is now deprecated. Check the rpc_backend parameter in the /etc/ceilometer/ceilometer.conf file is set to the following: 

rpc_backend=rabbit
Copy to Clipboard Toggle word wrap

This procedure upgrades the packages for the Compute service on all Controller nodes simultaneously.

  1. Stop all Compute resources in Pacemaker: 

    # pcs resource disable openstack-nova-novncproxy-clone
# pcs resource disable openstack-nova-consoleauth-clone
# pcs resource disable openstack-nova-conductor-clone
# pcs resource disable openstack-nova-api-clone
# pcs resource disable openstack-nova-scheduler-clone
    Copy to Clipboard Toggle word wrap
  2. Wait until the output of pcs status shows that the above services have stopped running.

  3. Upgrade the relevant packages: 

    # yum upgrade '*nova*'
    Copy to Clipboard Toggle word wrap

  4. Reload systemd to account for updated unit files: 

    # systemctl daemon-reload
    Copy to Clipboard Toggle word wrap

  5. Update the Compute database schema: 

    # su -s /bin/sh -c "nova-manage api_db sync" nova
# su -s /bin/sh -c "nova-manage db sync" nova
    Copy to Clipboard Toggle word wrap

  6. If you are performing a rolling upgrade of your compute hosts you need to set explicit API version limits to ensure compatibility between your Mitaka and Newton environments.

    Before starting Compute services on Controller or Compute nodes, set the compute option in the [upgrade_levels] section of nova.conf to the previous Red Hat OpenStack Platform version (mitaka): 

    # crudini --set /etc/nova/nova.conf upgrade_levels compute mitaka
    Copy to Clipboard Toggle word wrap

    This ensures the Controller node can still communicate to the Compute nodes, which are still using the previous version.

    You will need to first unmanage the Compute resources by running pcs resource unmanage on one Controller node: 

    # pcs resource unmanage openstack-nova-novncproxy-clone
# pcs resource unmanage openstack-nova-consoleauth-clone
# pcs resource unmanage openstack-nova-conductor-clone
# pcs resource unmanage openstack-nova-api-clone
# pcs resource unmanage openstack-nova-scheduler-clone
    Copy to Clipboard Toggle word wrap

    Restart all the services on all controllers: 

    # openstack-service restart nova
    Copy to Clipboard Toggle word wrap

    You should return control to the Pacemaker after upgrading all of your compute hosts to Red Hat OpenStack Platform 10. 

    # pcs resource manage openstack-nova-scheduler-clone
# pcs resource manage openstack-nova-api-clone
# pcs resource manage openstack-nova-conductor-clone
# pcs resource manage openstack-nova-consoleauth-clone
# pcs resource manage openstack-nova-novncproxy-clone
    Copy to Clipboard Toggle word wrap

  7. Clean up all Compute resources in Pacemaker: 

    # pcs resource cleanup openstack-nova-scheduler-clone
# pcs resource cleanup openstack-nova-api-clone
# pcs resource cleanup openstack-nova-conductor-clone
# pcs resource cleanup openstack-nova-consoleauth-clone
# pcs resource cleanup openstack-nova-novncproxy-clone
    Copy to Clipboard Toggle word wrap

  8. Restart all Compute resources in Pacemaker: 

    # pcs resource enable openstack-nova-scheduler-clone
# pcs resource enable openstack-nova-api-clone
# pcs resource enable openstack-nova-conductor-clone
# pcs resource enable openstack-nova-consoleauth-clone
# pcs resource enable openstack-nova-novncproxy-clone
    Copy to Clipboard Toggle word wrap
  9. Wait until the output of pcs status shows that the above resources are running.

6.10. Upgrading Clustering service (sahara)
Copy link

This procedure upgrades the packages for the Clustering service on all Controller nodes simultaneously.

  1. Stop all Clustering service resources in Pacemaker: 

    # pcs resource disable openstack-sahara-api-clone
# pcs resource disable openstack-sahara-engine-clone
    Copy to Clipboard Toggle word wrap
  2. Wait until the output of pcs status shows that the above services have stopped running.

  3. Upgrade the relevant packages: 

    # yum upgrade '*sahara*'
    Copy to Clipboard Toggle word wrap

  4. Reload systemd to account for updated unit files: 

    # systemctl daemon-reload
    Copy to Clipboard Toggle word wrap

  5. Update the Clustering service database schema: 

    # su -s /bin/sh -c "sahara-db-manage upgrade heads" sahara
    Copy to Clipboard Toggle word wrap

  6. Clean up the Clustering service using Pacemaker: 

    # pcs resource cleanup openstack-sahara-api-clone
# pcs resource cleanup openstack-sahara-engine-clone
    Copy to Clipboard Toggle word wrap

  7. Restart all Block Storage service resources in Pacemaker: 

    # pcs resource enable openstack-sahara-api-clone
# pcs resource enable openstack-sahara-engine-clone
    Copy to Clipboard Toggle word wrap
  8. Wait until the output of pcs status shows that the above resources are running.

6.11. Upgrading OpenStack Networking (neutron)
Copy link

This procedure upgrades the packages for the Networking service on all Controller nodes simultaneously.

  1. Prevent Pacemaker from triggering the OpenStack Networking cleanup scripts: 

    # pcs resource unmanage neutron-ovs-cleanup-clone
# pcs resource unmanage neutron-netns-cleanup-clone
    Copy to Clipboard Toggle word wrap

  2. Stop OpenStack Networking resources in Pacemaker: 

    # pcs resource disable neutron-server-clone
# pcs resource disable neutron-openvswitch-agent-clone
# pcs resource disable neutron-dhcp-agent-clone
# pcs resource disable neutron-l3-agent-clone
# pcs resource disable neutron-metadata-agent-clone
    Copy to Clipboard Toggle word wrap

  3. Upgrade the relevant packages: 

    # yum upgrade 'openstack-neutron*' 'python-neutron*'
    Copy to Clipboard Toggle word wrap

  4. Update the OpenStack Networking database schema: 

    # su -s /bin/sh -c "neutron-db-manage upgrade heads" neutron
    Copy to Clipboard Toggle word wrap

  5. Clean up OpenStack Networking resources in Pacemaker: 

    # pcs resource cleanup neutron-metadata-agent-clone
# pcs resource cleanup neutron-l3-agent-clone
# pcs resource cleanup neutron-dhcp-agent-clone
# pcs resource cleanup neutron-openvswitch-agent-clone
# pcs resource cleanup neutron-server-clone
    Copy to Clipboard Toggle word wrap

  6. Restart OpenStack Networking resources in Pacemaker: 

    # pcs resource enable neutron-metadata-agent-clone
# pcs resource enable neutron-l3-agent-clone
# pcs resource enable neutron-dhcp-agent-clone
# pcs resource enable neutron-openvswitch-agent-clone
# pcs resource enable neutron-server-clone
    Copy to Clipboard Toggle word wrap

  7. Return the cleanup agents to Pacemaker control: 

    # pcs resource manage neutron-ovs-cleanup-clone
# pcs resource manage neutron-netns-cleanup-clone
    Copy to Clipboard Toggle word wrap
  8. Wait until the output of pcs status shows that the above resources are running.

6.12. Upgrading Compute (nova) Nodes
Copy link

This procedure upgrades the packages for on a single Compute node. Run this procedure on each Compute node individually.

If you are performing a rolling upgrade of your compute hosts you need to set explicit API version limits to ensure compatibility between your Mitaka and Newton environments.

Before starting Compute services on Controller or Compute nodes, set the compute option in the [upgrade_levels] section of nova.conf to the previous Red Hat OpenStack Platform version (mitaka): 

# crudini --set /etc/nova/nova.conf upgrade_levels compute mitaka
Copy to Clipboard Toggle word wrap

Before updating, take a systemd snapshot of the OpenStack Platform services. 

# systemctl snapshot openstack-services
Copy to Clipboard Toggle word wrap

This ensures the Controller node can still communicate to the Compute nodes, which are still using the previous version.

  1. Stop all OpenStack services on the host: 

    # systemctl stop 'openstack*' '*nova*'
    Copy to Clipboard Toggle word wrap

  2. Upgrade all packages: 

    # yum upgrade
    Copy to Clipboard Toggle word wrap

  3. Start all OpenStack services on the host: 

    # openstack-service start
    Copy to Clipboard Toggle word wrap

  4. After you have upgraded all of your hosts, remove the API limits configured in the previous step. On all of your hosts: 

    # crudini --del /etc/nova/nova.conf upgrade_levels compute
    Copy to Clipboard Toggle word wrap

  5. Restart all OpenStack services on the host: 

    # systemctl isolate openstack-services.snapshot
    Copy to Clipboard Toggle word wrap

6.13. Post-Upgrade Tasks
Copy link

After completing all of your individual service upgrades, you should perform a complete package upgrade on all nodes: 

# yum upgrade
Copy to Clipboard Toggle word wrap

This will ensure that all packages are up-to-date. You may want to schedule a restart of your OpenStack hosts at a future date in order to ensure that all running processes are using updated versions of the underlying binaries.

Review the resulting configuration files. The upgraded packages will have installed .rpmnew files appropriate to the Red Hat OpenStack Platform 10 version of the service.

New versions of OpenStack services may deprecate certain configuration options. You should also review your OpenStack logs for any deprecation warnings, because these may cause problems during a future upgrade. For more information on the new, updated and deprecated configuration options for each service, see Configuration Reference available from Red Hat OpenStack Platform Documentation Suite.

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top