starlingx/docs
Code Issues Proposed changes
docs/doc/source/dist_cloud/kubernetes/customizing-the-update-configuration-for-distributed-cloud-update-orchestration.rst
Ron Stone a9f6845ab0 Re-arranged DC Horizon page 
Image and related text updates.
Some associated rST markup changes for consistency.
Updates for patchset 1 review comments.
Substantial new content to better cover Horizon usage.
Updates for patchset 3 review comments.
Updates for patchset 4 review comments.
Updates for patchset 5 review comments.
Fix typo.
Fix numbering in procedures.
Updates for patchset 8 review comments.
Clarified **Subcloud** option description.
Remove redundant sentence.
Changes to image usage to remove duplication.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I53d93b93629851c07d0cd95ef1fb9c6f3fd9a0a5
2022-06-23 06:54:12 -04:00

3.5 KiB
Raw Blame History

Customize the Update Configuration for Distributed Cloud Update Orchestration

You can adjust how the nodes in each system (Central Cloud's RegionOne and/or Subclouds) are updated.

The update strategy for Update Orchestration uses separate configuration settings to control how the nodes on a given system are updated. You can adjust the settings used by default for Central Cloud's RegionOne and all subclouds, and you can create custom settings for individual subclouds.

You can change the configuration settings before or after creating a update strategy for update orchestration. The settings are maintained independently.

  1. Select the SystemController region.

  2. Select Distributed Cloud Admin > Orchestration.

  3. On the Orchestration page, select the Cloud Patching Configuration tab.

    image

    Take one of the following actions:

    • To edit the settings applicable to RegionOne and all subclouds by default, click Edit Configuration in the all clouds default row.

      image

      To save your changes, click Edit Cloud Patching Configuration.

    • To create custom settings for an individual subcloud, click Create New Cloud Patching Configuration.

      image

      In the Subcloud field, select the subcloud for the custom settings.

      To save your configuration changes, click Create Cloud Patching Configuration. The new configuration is added to the list.

      image

    The following settings are available:

    Subcloud

    This specifies the subcloud affected by the configuration. For the all clouds default configuration, this setting cannot be changed.

    Storage Apply Type

    Parallel or Serial — determines whether storage nodes are patched in parallel or serially

    Worker Apply Type

    Parallel or Serial — determines whether worker nodes are patched in parallel or serially

    Maximum Parallel Worker Hosts

    This sets the maximum number of worker nodes that can be patched in parallel.

    Default Instance Action

    Note

    This parameter is only applicable to hosted application VMs with the -openstack application.

    migrate or stop-start — determines whether hosted application VMs are migrated or stopped and restarted when a worker host is upgraded

    Alarm Restrictions

    Relaxed or Strict — determines whether the orchestration is aborted for alarms that are not management-affecting.

For information about creating and applying a patch strategy, see Update Management for Distributed Cloud <update-management-for-distributed-cloud>.

Related information

Creating an Update Strategy for Distributed Cloud Update Orchestration <creating-an-update-strategy-for-distributed-cloud-update-orchestration>

Applying the Update Strategy for Distributed Cloud <applying-the-update-strategy-for-distributed-cloud>