Note
This feature is available starting from the MCP 2019.2.5 maintenance update. Before enabling the feature, follow the steps described in Apply maintenance updates.
This section instructs you on how to upgrade the Galera cluster automatically through Jenkins using the Deploy - upgrade Galera cluster pipeline job.
To upgrade Galera:
Log in to the Salt Master node.
Open the cluster level of your deployment model.
Include the Galera upgrade pipeline job to DriveTrain:
In the classes/cluster/<cluster_name>/cicd/control/leader.yml
file,
add the following class:
classes:
- system.jenkins.client.job.deploy.update.upgrade_galera
Apply the jenkins.client state on the Jenkins nodes:
salt -C 'I@jenkins:client' state.sls jenkins.client
In the classes/cluster/<cluster_name>/infra/init.yml
file, set the
openstack_upgrade_enabled
parameter to true
:
parameters:
_param:
openstack_upgrade_enabled: true
Refresh pillars on the dbs*
nodes:
salt 'dbs*' saltutil.refresh_pillar
Add repositories with new Galera packages:
Apply the linux.system.repo state on the dbs*
nodes:
salt 'dbs*' state.sls linux.system.repo
Update the /etc/salt/minion.d/_orchestration.conf
file:
salt 'cfg*' state.sls salt.master
Warning
Verify that you have installed the latest Galera Salt
formula and it is present in
/etc/salt/minion.d/_orchestration.conf
. The file should
include the galera
line.
Log in to the Jenkins web UI.
Open the Deploy - upgrade Galera cluster pipeline.
Specify the following parameters as required:
Parameter |
Description |
---|---|
|
Mode to get the detailed description of the pipeline job flow through the stages. |
|
Shuts down all MySQL instances on the target nodes during upgrade. |
|
Upgrades system packages including kernel using
|
|
Upgrades all installed applications using |
|
Defines the Salt Master node credentials to use for connection,
defaults to |
|
Defines the Salt Master node host URL with the |
|
Adds the target database server nodes. Defaults to |
Click Deploy.
To monitor the deployment process, follow the instructions in MCP Deployment Guide: View the deployment details.
Stage |
Description |
---|---|
Pre-upgrade |
Only non-destructive actions are applied during this phase. Basic service verification is performed. The job is launched on all target servers before moving to the next stage. |
Stop the Galera cluster |
All Galera clusters are stopped on the OpenStack APIs are not accessible starting from this point. This does not affect the data plane services such as OVS or KVM nodes. |
Upgrade Galera |
The Galera code is upgraded. No workload downtime is expected. |
Upgrade OS |
Optional. Launches only if |
Start the Galera cluster |
The Galera cluster is being started on the |
Revert the changes in the classes/cluster/<cluster_name>/infra/init.yml
file made during step 3.3.