Ask Your Question

Revision history [back]

planning an OpenStack upgrade

The following points will help you plan for a successful OpenStack upgrade:

Identify any potential incompatibilities between releases by reading the OpenStack release notes. Decide on the appropriate method for the upgrade. Ensure that you are able to roll back if the upgrade fails. Ensure that your data is backed up, including configuration files and databases. Based on SLAs for your services, determine the acceptable downtime and inform users about the downtime in advance. Use a test environment to verify that the selected upgrade method will work for your production environment.

Prerequisites

Before you upgrade, clean the environment to ensure a consistent state. For example, if some instances are not fully purged from the system after deletion, unexpected behavior might occur.

For environments using the OpenStack Networking service (neutron), verify the release version of the database.

Taking a Backup

Take a backup of the current configurations and database. Save the configuration files on all nodes. Upgrading OpenStack Sequence for upgrading services

The sequence for upgrading the OpenStack services is important as upgrading services in wrong order can break the cloud easily. The following order is recommended:

Upgrade database Upgrade RabbitMQ Upgrade Memcached Upgrade OpenStack Identity service (Keystone) Upgrade the OpenStack image service (Glance) Upgrade OpenStack compute (Nova) Upgrade OpenStack networking (Neutron) Upgrade the OpenStack dashboard (Horizon) Upgrade the OpenStack orchestration (Heat)

refer to : https://developer.ibm.com/in/2017/11/27/

refer to: https://docs.openstack.org/tripleo-docs/latest/install/post_deployment/upgrade.html

planning an OpenStack upgrade

The following points will help you plan for a successful OpenStack upgrade:

Identify any potential incompatibilities between releases by reading the OpenStack release notes.
 Decide on the appropriate method for the upgrade.
 Ensure that you are able to roll back if the upgrade fails.
 Ensure that your data is backed up, including configuration files and databases.
 Based on SLAs for your services, determine the acceptable downtime and inform users about the downtime in advance.
 Use a test environment to verify that the selected upgrade method will work for your production environment.

environment.

Prerequisites

Before you upgrade, clean the environment to ensure a consistent state. For example, if some instances are not fully purged from the system after deletion, unexpected behavior might occur.

occur. For environments using the OpenStack Networking service (neutron), verify the release version of the database.

database.

Taking a Backup

Take a backup of the current configurations and database. Save the configuration files on all nodes. Upgrading OpenStack Sequence for upgrading services

The sequence for upgrading the OpenStack services is important as upgrading services in wrong order can break the cloud easily. The following order is recommended:

Upgrade database
Upgrade RabbitMQ
Upgrade Memcached
Upgrade OpenStack Identity service (Keystone)
Upgrade the OpenStack image service (Glance)
Upgrade OpenStack compute (Nova)
Upgrade OpenStack networking (Neutron)
Upgrade the OpenStack dashboard (Horizon)
Upgrade the OpenStack orchestration (Heat)

(Heat)

refer to : https://developer.ibm.com/in/2017/11/27/

refer to: https://docs.openstack.org/tripleo-docs/latest/install/post_deployment/upgrade.html