This section describes how to restore the MAAS PostgreSQL database and the Salt Master node using the Backupninja Jenkins pipeline job.
To restore the services using the Jenkins pipeline job:
Verify that you have completed the steps described in Configure the Backupninja restore pipeline.
Log in to the Jenkins web UI.
Select from the following options:
For MCP versions prior to 2019.2.6, open the Backupninja restore salt-master/MaaS backup pipeline job.
For MCP versions starting from 2019.2.6, open the Backupninja restore pipeline pipeline job.
Specify the required parameters:
Parameter |
Description and values |
---|---|
SALT_MASTER_URL |
Add the IP address of your Salt Master node host and the
|
CREDENTIALS_ID |
Add |
RESTORE_SALTMASTER_AND_MAAS Added since 2019.2.6 |
Select to restore Salt Master and MAAS. |
RESTORE_KEYSTONE_CREDENTIAL_KEYS Added since 2019.2.12 |
Select to restore the Keystone credential keys. |
Click Build.
The Jenkins pipeline job workflow:
Pillar verification. Verify that initial_data
in pillars are
defined correctly to prevent any issues related to a wrong
configuration during the execution of the pipeline job.
Perform the restore.
Verify that the restore completed and, in case of a remote backup storage, moved correctly:
Verify the Salt Master node:
Verify the Salt keys in /etc/salt/pki/
.
Verify the model in /srv/salt/reclass
.
Try to perform a test ping on the available Salt Minions using
test.ping
.
Verify MAAS:
Verify the MAAS UI.
List the available machines in MAAS through
the maasng.list_machines
Salt module.