Redeploy a Subcloud with Redfish Platform Management Service

For subclouds with servers that support Redfish Virtual Media Service (version 1.2 or higher), you can use the Central cloud’s CLI to redeploy the ISO and bootstrap subclouds from the Central cloud.

Caution

All application and data on the subcloud will be lost after redeployment.

Any records of FPGA device image updates on the subcloud will be lost. You will need to reapply the FPGA device image update orchestration procedure. For more information, see Device Image Update Orchestration.

About this task

The subcloud redeployment has these phases:

Executing the dcmanager subcloud redeploy command in the Central Cloud:

  • Uses Redfish Virtual Media Service to remote install the ISO on controller-0 in the subcloud.

  • Uses Ansible to bootstrap StarlingX on controller-0.

Prerequisites

  • The install values are required for subcloud redeployment. By default, install values are stored in database after a subcloud installation or upgrade, and the redeployment will re-use these values. You can use the following CLI command in the Central cloud to update them if necessary:

    ~(keystone_admin)]$ dcmanager subcloud update subcloud1 --install-values\ install-values.yml --bmc-password <password>

    For more information on install-values.yml file, see Install a Subcloud Using Redfish Platform Management Service.

    You can only redeploy the same software version with the Central cloud on the subcloud. If the software version of the subcloud is not same as the System Controller, the redeploy command will update the software version of the subcloud and install the correct version afterwards.

  • Check the subcloud’s availability in the Central cloud.

    For example:

    ~(keystone_admin)]$ dcmanager subcloud list

 +----+----------+------------+--------------+---------------+---------+
 | id | name     | management | availability | deploy status | sync    |
 +----+----------+------------+--------------+---------------+---------+
 | 1  | subcloud1| unmanaged  | offline      | complete      | unknown |
 +----+----------+------------+--------------+---------------+---------+

    As the redeploy will cause data and application loss, it is not necessary and not recommended to redeploy a healthy subcloud. Redeployment request of a managed or online subcloud will therefore be rejected.

Procedure

  1. Create the subcloud bootstrap-values.yml file if it is not available already. This file contains the configuration parameters used to bootstrap the controller-0 of the subcloud that differ from the default bootstrap values.

    For more information on bootstrap-values.yml file, see Install a Subcloud Using Redfish Platform Management Service.

  2. Execute the redeploy CLI.

    For example:

    ~(keystone_admin)]$ dcmanager subcloud redeploy subcloud1 --bootstrap-values /home/sysadmin/subcloud1-bootstrap-values.yml –sysadmin-password <sysadmin_password>

  3. Confirm the redeploy of the subcloud.

    You are prompted to enter redeploy to confirm the redeployment.

    Warning

    This will redeploy the subcloud. All applications and data on the subcloud will be lost.

    Any records of FPGA device image updates on the subcloud will be lost. You will need to reapply the FPGA device image update orchestration procedure. For more information, see Device Image Update Orchestration.

    Please type redeploy to confirm: redeploy

    Any other input will abort the redeployment.

  4. In the Central cloud, monitor the progress of the subcloud installation and bootstrapping by viewing the deploy status field of the dcmanager subcloud list command.

    For example:

    ~(keystone_admin)]$ dcmanager subcloud list

 +----+-----------+------------+--------------+---------------+---------+
 | id | name      | management | availability | deploy status | sync    |
 +----+-----------+------------+--------------+---------------+---------+
 | 1  | subcloud1 | unmanaged  | offline      | installing    | unknown |
 +----+-----------+------------+--------------+---------------+---------+

    For more information on the deploy status filed, see Install a Subcloud Using Redfish Platform Management Service.

    You can also monitor detailed logging of the subcloud installation and bootstrapping by monitoring the following log file on the active controller in the Central cloud:

    • /var/log/dcmanager/ansible/subcloud1_playbook_output.log

  5. After the subcloud is successfully redeployed and bootstrapped, run the dcmanager subcloud deploy config command to complete the process. The subcloud availability status will change from offline to online when the reconfiguration is complete. For more information, see Manage Subclouds Using the CLI.

Important

Limitation: When you perform a touchless subcloud install with Redfish using the dcmanager subcloud add command for all servers with iDRAC 9 firmware installed, the subcloud install fails due to an ISO image insertion mount failure over an IPv6 network Distributed Cloud system.

Workaround: For all Dell servers with iDRAC 9 firmware installed with version 5.10.00.00 or below, System administrators must perform the following steps:

Procedure

  1. Log in to the iDRAC 9 web interface and select, Configuration > Virtual Console from the drop-down menu.

  2. Select HTML5 (or any other option except eHTML5) from the Plug-in Type drop-down menu.

  3. Click Apply to apply the change.

Postrequisites

  • Provision the newly installed and bootstrapped subcloud. For detailed StarlingX deployment procedures for the desired deployment configuration of the subcloud, see the post-bootstrap steps of the Installation guide.

  • Check and update docker registry credentials on the subcloud:

    REGISTRY="docker-registry"
SECRET_UUID='system service-parameter-list | fgrep
$REGISTRY | fgrep auth-secret | awk '{print $10}''
SECRET_REF='openstack secret list | fgrep $
{SECRET_UUID} | awk '{print $2}''
openstack secret get ${SECRET_REF} --payload -f value

    The secret payload should be username: sysinv password:<password>. If the secret payload is username: admin password:<password>, see, Updating Docker Registry Credentials on a Subcloud for more information.

  • For more information on bootstrapping and deploying, see the procedures listed under Installation.