Install and Provision a Subcloud

You can install and provision a subcloud with or without using the 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 install the ISO and bootstrap subclouds from the Central Cloud. For more information, see Installing a Subcloud Using Redfish Platform Management Service.

For subclouds with servers that do not support Redfish Virtual Media Service, the ISO is installed locally at the subcloud. You can use the Central Cloud’s CLI to bootstrap subclouds from the Central Cloud. For more information, see Installing a Subcloud Without Redfish Platform Management Service.

Note

Each subcloud must be on a separate management subnet (different from the SystemController and from any other subclouds).

Reinstall 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 re-install the ISO and bootstrap subclouds from the Central Cloud.

Caution

All application and data on the subcloud will be lost after re-installation.

About this task

The subcloud reinstallation has two phases:

Executing the dcmanager subcloud reinstall 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 reinstallation. By default, install values are stored in the database after a subcloud installation or upgrade, and the reinstallation will re-use the install values. If you want to update the install values, use the following CLI command in the Central Cloud.

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

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

    You can only reinstall the same software version with the Central Cloud on the subcloud.

  • 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 reinstall will cause data and application loss, it is not necessary and not recommended to reinstall a healthy subcloud. The dcmanager rejects the reinstallation of a managed or online subcloud.

Procedure

  1. Execute the reinstall using the CLI. For example,

    ~(keystone_admin)]$ dcmanager subcloud reinstall subcloud1
    
  2. Confirm the reinstall of the subcloud.

    You are prompted to enter reinstall to confirm the reinstallation.

    Warning

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

    Please type reinstall to confirm: reinstall

    Any other input will abort the reinstallation.

  3. At the Central Cloud, monitor the progress of the subcloud installation and bootstrapping by using 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 Installing a Subcloud Using Redfish Platform Management Service.

    You can also monitor detailed logging of the subcloud installation, bootstrapping by monitoring the following log files on the active controller in the Central Cloud.

    • /var/log/dcmanager/subcloud_name_install_date_stamp.log

    • /var/log/dcmanager/subcloud_name_bootstrap_date_stamp.log

  4. After the subcloud is successfully reinstalled and bootstrapped, use the following command to reconfigure the subcloud, subcloud reconfig. For more information, see Managing Subclouds Using the CLI.