starlingx/docs
Code Issues Proposed changes
docs/doc/source/dist_cloud/kubernetes/update-orchestration-of-central-clouds-regionone-and-subclouds.rst
Elisamara Aoki Goncalves 9bc86e4e31 Unified Software Delivery & Mgmt: HORIZON changes(USM) 
Update images of the Horizon GUI with new terms and tabs names.
Update procedures for Horizon GUI.

Story: 2010676
Task: 50731

Change-Id: I9c8fa7b778a45bdcf764ddb5a9a7dc7185eb012b
Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com>
2024-10-16 14:04:28 +00:00

3.5 KiB
Raw Blame History

Update Orchestration of Subclouds

You can use update orchestration to automate software updates across all subclouds in the .

You can use the Horizon Web interface or the CLI. To use the CLI, see update-orchestration-of-central-clouds-regionone-and-subclouds-using-the-cli.

Note

Patch orchestration is the recommended method for updating software on a system. Do not update individual subclouds manually.

To use update orchestration, complete the following workflow:

  1. Ensure that the required updates are uploaded and applied to the SystemController / central update repository.

    For more information, see uploading-and-applying-updates-to-systemcontroller-using-horizon.

  2. Update the RegionOne, for more information see uploading-and-applying-updates-to-systemcontroller-using-horizon-update-the-regionone.

  3. Create an update strategy for the update orchestration.

    See creating-an-update-strategy-for-distributed-cloud-update-orchestration.

  4. Optionally, customize the configuration settings used by the update strategy.

    The update strategy is applied to all subclouds using default configuration settings. You can change these settings, and you can create custom settings for individual subclouds. For more information, see customizing-the-update-configuration-for-distributed-cloud-update-orchestration.

  5. Apply the strategy for the update orchestration.

    See applying-the-update-strategy-for-distributed-cloud.

    As each subcloud is updated, it moves through the following states:

    • For software deployment of a patch:
      Initial

      The update has not started.

      Precheck

      Subcloud alarm status is being checked for management-affecting alarms.

      Create VIM strategy

      The strategy is being created in the subcloud.

      Apply VIM strategy

      The strategy is being applied in the subcloud.

      Finish strategy

      Updates that are no longer required are being deleted.

      Updates that require committing are being committed.

      Complete

      Updating has been completed successfully.

    • For software deployment of a major release (upgrade):
      Initial

      The update has not started.

      Precheck

      Subcloud alarm status is being checked for management-affecting alarms.

      Install license

      Installing release license.

      Create VIM strategy

      The strategy is being created in the subcloud.

      Apply VIM strategy

      The strategy is being applied in the subcloud.

      Finish strategy

      Updates that are no longer required are being deleted.

      Updates that require committing are being committed.

      Complete

      Updating has been completed successfully.

    During this process, alarms 900.001 and 900.101 are raised temporarily.

creating-an-update-strategy-for-distributed-cloud-update-orchestration

customizing-the-update-configuration-for-distributed-cloud-update-orchestration

applying-the-update-strategy-for-distributed-cloud