starlingx/docs
Code Issues Proposed changes

Merge "After upgrade DC Patch orchestration strategy is created only on the central cloud"

Browse Source
This commit is contained in:
Zuul 2022-01-28 18:58:05 +00:00 committed by Gerrit Code Review
commit df60ca5f88
1 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
doc/source/dist_cloud/kubernetes/creating-an-update-strategy-for-distributed-cloud-update-orchestration.rst
View File

@ -10,6 +10,13 @@ To update Central Cloud's RegionOne and the subclouds with updates in the
**Partial-Apply** state, you must create an update strategy for |prod-dc| **Partial-Apply** state, you must create an update strategy for |prod-dc|
Update Orchestration. Update Orchestration.
After a patch (update) has been **applied/removed/committed** on the
Central Cloud's RegionOne, the subclouds are audited and their patching sync
status is updated. This can take up to 15 minutes.
If the Subclouds are in a **Managed** state and if the patching sync status is
"out-of-sync", it can be orchestrated.
.. rubric:: |context| .. rubric:: |context|
Only one update strategy can exist at a time. The strategy controls how the Only one update strategy can exist at a time. The strategy controls how the
@ -41,28 +48,28 @@ You must be in **SystemController** mode. To change the mode, see
In the Create Strategy dialog box, adjust the settings as needed. In the Create Strategy dialog box, adjust the settings as needed.
**Strategy Type** **Strategy Type**
Patch, Upgrade, Kubernetes, or Firmware. Patch, Upgrade, Kubernetes, or Firmware.
**Apply to** **Apply to**
Subcloud or Subcloud Group. Subcloud or Subcloud Group.
**Subcloud** **Subcloud**
Write the subcloud name. Write the subcloud name.
**Subcloud Group** **Subcloud Group**
Write the subcloud group name, only if you select the **Apply to: Subcloud Group** option. Write the subcloud group name, only if you select the **Apply to: Subcloud Group** option.
**Stop on Failure** **Stop on Failure**
default true — determines whether update orchestration failure for a default true — determines whether update orchestration failure for a
subcloud prevents application to subsequent subclouds. subcloud prevents application to subsequent subclouds.
**Subcloud Apply Type** **Subcloud Apply Type**
Parallel or Serial, default Parallel — determines whether the subclouds Parallel or Serial, default Parallel — determines whether the subclouds
are updated in parallel or serially. are updated in parallel or serially.
**Maximum Parallel Subclouds** **Maximum Parallel Subclouds**
default 20 — If this is not specified using the |CLI|, the values for 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 max_parallel_subclouds defined for each subcloud group will be used by
default. default.
@ -81,7 +88,7 @@ You must be in **SystemController** mode. To change the mode, see
#. Click **Create Strategy**. #. Click **Create Strategy**.
Only subclouds in the Managed state and whose patching sync status is 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, 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 you must delete the update strategy and create a new one. Confirmation
before applying strategy will be needed. If the created strategy is older before applying strategy will be needed. If the created strategy is older