Note
This feature is available starting from the MCP 2019.2.12 maintenance update. Before using the feature, follow the steps described in Apply maintenance updates.
Using the Deploy - Openstack Database Cleanup Jenkins pipeline job,
you can automatically clean up stale records from the Nova, Cinder, or Heat
database to make it smaller. This is helpful before any update or upgrade
activity. You can execute the Deploy - Openstack Database Cleanup
Jenkins pipeline job without a maintenance window, just as for an online
dbsync
.
To clean up an OpenStack database:
Open your Git project repository with the Reclass model on the cluster level.
In <cluster_name>/openstack/control.yml
, specify the following
pillars setting the db_purge
parameter to True
and the days
parameter as required. If you skip setting the days
parameter, all
stale records will be archived or purged for Nova and Heat. For Cinder on
OpenStack Pike, records older than 1 day will be deleted.
For example:
For Nova:
nova:
controller:
db_purge:
enabled: True
days: 45
For Cinder:
cinder:
controller:
db_purge:
enabled: True
days: 45
For Heat:
heat:
server:
db_purge:
enabled: True
days: 45
Log in to the Jenkins web UI.
Open the Deploy - Openstack Database Cleanup Jenkins pipeline job.
Specify the following parameters:
Parameter |
Description and values |
---|---|
SALT_MASTER_CREDENTIALS |
The Salt Master credentials to use for connection, defaults to
|
SALT_MASTER_URL |
The Salt Master node host URL with the |
Click Deploy.
The Jenkins pipeline job workflow:
For Nova, move the deleted rows from the production tables to shadow tables.
For Cinder, purge the database entries that are marked as deleted.
For Heat, purge the database entries that are marked as deleted.