The OpenStack data plane includes the servers that host end-user data applications. More specifically, these hosts include compute, storage, and gateway nodes. Depending on the upgrade requirements, you can apply any kind of the upgrade depths while upgrading the data plane.
To upgrade the data plane of your OpenStack deployment:
To upgrade the gateway nodes, select one of the following options:
Caution
Skip this step if your MCP OpenStack deployment includes the OpenContrail component because such configuration does not contain gateway nodes.
Non-HA routers are present in the cloud:
Migrate the non-HA routers from the target nodes using the Neutron service and the following commands in particular:
Log in to the Jenkins web UI.
Run the Deploy - upgrade OVS gateway pipeline for the gateway nodes which you have migrated the workloads from.
Note
Run the pipeline in the interactive mode to get the detailed description of the pipeline flow through the stages.
Note
Since all resources have already been migrated from the
nodes, we recommend performing the full upgrade including
OS_UPGRADE
and OS_DIST_UPGRADE
.
Migrate the non-HA routers back and rerun the Deploy - upgrade OVS gateway pipeline for the rest of the gateway nodes.
Verify that the gateway components are reconnected to the control plane.
Non-HA routers are not present in the cloud:
Log in to the Jenkins web UI.
Run the Deploy - upgrade OVS gateway pipeline for all gateway nodes specifying TARGET_SERVERS=’gtw*’.
Note
Run the pipeline in the interactive mode to get the detailed description of the pipeline flow through the stages.
Verify that the gateway components are reconnected to the control plane.
Caution
Skip this step if your MCP OpenStack deployment includes the OpenContrail component because such configuration does not contain gateway nodes.
Upgrade the OpenStack compute nodes.
Estimate and minimize the risks and address the limitations of live migration.
The limitations of the live migration technology include:
Warning
Before proceeding with live migration in a production environment, assess these risks thoroughly.
active
memory pages. If the number of pages
that are being written to all the time is big, the migration process
will never finish. High-memory, high-load Windows virtual machines are
known to have this particular issue.Perform the live migration of workloads.
Log in to the Jenkins web UI.
Run the Deploy - upgrade computes pipeline to upgrade the OpenStack compute nodes which you have migrated the workloads from. It is essential that you upgrade the compute nodes by small batches.
Caution
The impact of the upgrade process should be calculated for each compute node during the planning stage as this step may take a significant amount of time.
Note
Run the pipeline in the interactive mode to get the detailed description of the pipeline flow through the stages.
Migrate the workloads back and rerun the Deploy - upgrade computes pipeline for the rest of the compute nodes.
Verify that the compute nodes are reconnected to the control plane.
Proceed to Perform the post-upgrade activities.