starlingx/docs
Code Issues Proposed changes
Files
3e51eb1421d89d1abe2ad755e645c8017b2957a5
docs/doc/source/dist_cloud/kubernetes/creating-an-update-strategy-for-distributed-cloud-update-orchestration.rst
Juanita-Balaraj 265d96bed1 Fixed \_ as the output was not rendering correctly (pick r5 updates only) 
Fixed Patchset 4 comments
Fixed Patchset 3 comments and added additional updates
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
Change-Id: I7482afc3a90bbdc94b6ecd8b6ac39d831b8a45db
Signed-off-by: Juanita-Balaraj <juanita.balaraj@windriver.com>
2021-11-02 11:27:15 -04:00

3.1 KiB
Raw Blame History

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>.

  1. Select the SystemController region.

  2. Select Distributed Cloud Admin > Software Management.

  3. On the Software Management page, select the Cloud Patching Orchestration tab.

    image

  4. On the Cloud Patching Orchestration tab, click Create Strategy.

    In the Create Patch Strategy dialog box, adjust the settings as needed.

    image

    subcloud-apply-type

    parallel or serial — determines whether the subclouds are updated in parallel or serially.

    If this is not specified using the , the values for subcloud_update_type defined for each subcloud group will be used by default.

    max-parallel-subclouds

    Sets the maximum number of subclouds that can be updated in parallel (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.

    stop-on-failure

    true or false (default) — determines whether update orchestration failure for a subcloud prevents application to subsequent subclouds.

  5. 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>.

  6. Click Create Patch Strategy.

    Only subclouds in the Managed state and whose patching sync status is out-of-sync are added to the list.

    image

    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>