☰
Conductor Documentation

WRCP Simplex Subcloud Restore

Overview

The workflow ‘restore_subcloud’ in WRCP plugin is responsible for restoring a simplex subcloud on the current hardware server or on a new one.

Two options are available to trigger the workflow restore_subcloud:

Prerequisites

  1. System Controller must be in a healthy state.
  2. The subcloud to be restored must be visible from System Controller although it can be unhealthy.
  3. A deployment of System Controller where the subcloud to be restored is installed must be available in Conductor.
  4. If the subcloud is not in a state to be created backup, a backup file compatible with the current subcloud release version must already exist in System Controller.
  5. This feature is only applicable to simplex subclouds.

Restore using the Maintenance Operation

Start the restore_subcloud operation from Conductor UI: Operations - Maintenance page.

  1. Go to Conductor > Operations > Maintenance page and find the simplex subcloud that needs to be restored.

Example Maintenance page

  1. If System Mode is empty to this simplex subcloud, that means this subcloud is in an abnormal state, e.g. ‘offline’. The operation Subcloud Restore can still be applied to this subcloud. However, we need to manually add the label system-mode to this simplex subcloud.

Go to Conductor > Operations > System Inventory page, click the button Update Inventory for this subcloud and add the label system-mode and its value simplex.

Example System Inventory page

Example System Inventory Edits

  1. Click the button Subcloud Restore from the Operations menu on the left end of the page.

Example Subcloud Restore

  1. On the upcoming dialog, fill the values and click the button Restore Subcloud to start the workflow to restore the subcloud.

The following parameters are available:

Parameter Description
Replacement Management Mac Address The name of the secret that contains the username of bmc server. Required when restoring subcloud on a new server.
bmc address The address of bmc server. Required when restoring subcloud on a new server.
The secret name of subcloud server’s bmc username The name of the secret that contains the username of bmc server. Required when restoring subcloud on a new server.
The secret name of subcloud server’s bmc password The name of the secret that contains the password of bmc server. Required when restoring subcloud on a new server.

The workflow execution status can be observed from the Maintenance Contents list. The workflow can take 30 to 60 minutes to complete.

Restore using the WRCP Plugin workflow

  1. Start the restore_subcloud workflow from Conductor Deployment/Environment of System Controller. Note: The restore_subcloud workflow can’t be executed from subcloud deployments.

Example Restore Workflow

Example Execute Workflow

The available ‘restore_subcloud’ parameters are shown below:

restore_subcloud:
  mapping: wrcp_plugin.windriver_wrcp.restore_subcloud_workflow.restore_subcloud
  parameters:
    subcloud_name:
      description: The name of subcloud to restore.
      type: string
      required: True
    bmc_address:
      description: The address of a bmc server. Required when restoring subcloud on a new server.
      type: string
      default: ''
    bmc_username:
      description: The secret containing the username of a bmc server. Required when restoring subcloud on a new server.
      type: string
      default: ''
    bmc_password:
      description: The secret containing the password of a bmc server. Required when restoring subcloud on a new server.
      type: string
      default: ''
    replacement_management_mac:
      description: The management mac address. Required when restoring subcloud on a new server.
      type: string
      default: ''

A subcloud restore process can take 30 to 60 minutes to complete.

The subcloud restore progress can be verified using workflow logs or by running the command dcmanager subcloud list from system controller.