Update Orchestration of SubcloudsΒΆ
You can use update orchestration to automate software updates across all subclouds in the Distributed Cloud.
You can use the Horizon Web interface or the CLI. To use the CLI, see Update Orchestration of Subclouds Using the CLI.
Note
Patch orchestration is the recommended method for updating software on a Distributed Cloud system. Do not update individual subclouds manually.
To use update orchestration, complete the following workflow:
Ensure that the required updates are uploaded and applied to the SystemController / central update repository.
For more information, see Upload and Apply Updates to SystemController Using Horizon.
Update the RegionOne, for more information see Update the RegionOne.
Create an update strategy for the Distributed Cloud update orchestration.
See Create an Update Strategy for Distributed Cloud Update Orchestration.
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 Customize the Update Configuration for Distributed Cloud Update Orchestration.
Apply the strategy for the Distributed Cloud update orchestration.
See Apply the Update Strategy for Distributed Cloud.
As each subcloud is updated, it moves through the following states:
- initial
The update has not started.
- pre-check
Subcloud alarm status is being checked for management-affecting alarms.
- updating patches
Patches are being updated to synchronize with System Controller updates.
- creating strategy
The strategy is being created in the subcloud.
- applying strategy
The strategy is being applied in the subcloud.
- finishing
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.
