Create an Update Strategy for Distributed Cloud Update Orchestration¶
To update Central Cloud’s RegionOne and the subclouds with updates in the Partial-Apply state, you must create an update strategy for Distributed Cloud Update Orchestration.
About this task
Only one update strategy can exist at a time. The strategy controls how the subclouds are updated (for example, serially or in parallel).
To determine how the nodes on the Central Cloud’s RegionOne and each subcloud are updated, the update strategy refers to separate configuration settings available on the Cloud Patching Configuration tab.
You must be in SystemController mode. To change the mode, see RegionOne and SystemController Modes.
Select the SystemController region.
Select Distributed Cloud Admin > Software Management.
On the Software Management page, select the Cloud Patching Orchestration tab.
On the Cloud Patching Orchestration tab, click Create Strategy.
In the Create Patch Strategy dialog box, adjust the settings as needed.
parallel or serial — determines whether the subclouds are updated in parallel or serially.
If this is not specified using the CLI, the values for subcloud_update_type defined for each subcloud group will be used by default.
Sets the maximum number of subclouds that can be updated in parallel (default 20).
If this is not specified using the CLI, the values for max_parallel_subclouds defined for each subcloud group will be used by default.
true or false (default) — determines whether update orchestration failure for a subcloud prevents application to subsequent subclouds.
Adjust how nodes are updated on RegionOne and the subclouds.
Click Create Patch Strategy.
Only subclouds in the Managed state and whose patching sync status is out-of-sync are added to the list.
To change the update strategy settings, you must delete the update strategy and create a new one.