starlingx/docs
Code Issues Proposed changes

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

Browse Source 
Updated Patchset 3 comments
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Change-Id: I351cb02dcb4fdae74c1bd01e19247964ea0731df
This commit is contained in:
Juanita-Balaraj 2022-01-27 18:01:09 -05:00
parent 60e17b5104
commit aedbc16b2d
1 changed files with 14 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
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|
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|
Only one update strategy can exist at a time. The strategy controls how the
@ -81,7 +88,7 @@ You must be in **SystemController** mode. To change the mode, see
#. 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,
you must delete the update strategy and create a new one. Confirmation
before applying strategy will be needed. If the created strategy is older