08985b05ea
Added new topics on creating, editing, and deleting subcloud groups using Horizon New screenshots for subclouds, cloud strategy, and update orchestration Fixed after feedback Change-Id: I83c87c011a8bdd4ee6e6f3fb9d27d3536b788024 Signed-off-by: Keane Lim <keane.lim@windriver.com>
3.5 KiB
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 Update Orchestration.
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
<regionone-and-systemcontroller-modes>.
Select the SystemController region.
Select Distributed Cloud Admin > Software Management.
On the Software Management page, select the Cloud Strategy Orchestration tab.
On the Cloud Strategy Orchestration tab, click Create Strategy.
In the Create Strategy dialog box, adjust the settings as needed.
- Strategy Type
-
Patch, Upgrade, Kubernetes, or Firmware.
- Apply to
-
Subcloud or Subcloud Group.
- Subcloud
-
Write the subcloud name.
- Subcloud Group
-
Write the subcloud group name, only if you select the Apply to: Subcloud Group option.
- Stop on Failure
-
default true — determines whether update orchestration failure for a subcloud prevents application to subsequent subclouds.
- Subcloud Apply Type
-
Parallel or Serial, default Parallel — determines whether the subclouds are updated in parallel or serially.
- Maximum Parallel Subclouds
-
default 20 — If this is not specified using the , the values for max_parallel_subclouds defined for each subcloud group will be used by default.
- Force
-
default False.
Adjust how nodes are updated on RegionOne and the subclouds.
See
Customizing the Update Configuration for Distributed Cloud Update Orchestration <customizing-the-update-configuration-for-distributed-cloud-update-orchestration>.Click Create 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. Confirmation before applying strategy will be needed. If the created strategy is older than 60 minutes, a warning message will be displayed. The user can apply the strategy or verify if it is still valid.
Note
To change the update strategy settings, you must delete the update strategy and create a new one.
Customizing the Update Configuration for Distributed Cloud Update
Orchestration <customizing-the-update-configuration-for-distributed-cloud-update-orchestration>
Applying the Update Strategy for Distributed Cloud
<applying-the-update-strategy-for-distributed-cloud>