starlingx/docs
Code Issues Proposed changes
2b2cc0b045
docs/doc/source/dist_cloud/kubernetes/update-orchestration-of-central-clouds-regionone-and-subclouds.rst
Ron Stone 10805c3e8f Apply dir convention to DC 
Moved all DC content under a kubernetes directory. This is needed
to allow title versioning distinctions in partner builds.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ia7ab4fccc7cb9ed6c242cf584f237165f00e5ef2
2021-08-03 07:57:24 -04:00

3.3 KiB
Raw Blame History

Update Orchestration of Central Cloud's RegionOne and Subclouds

You can use update orchestration to automate software updates across the Central Cloud's RegionOne and all subclouds in the .

You can use the Horizon Web interface or the CLI. To use the CLI, see Update Orchestration of Central Cloud's RegionOne and Subclouds Using the CLI <update-orchestration-of-central-clouds-regionone-and-subclouds-using-the-cli>.

Note

Patch orchestration is the recommended method for updating software on a system. Do not update RegionOne or individual subclouds manually.

To use update orchestration, complete the following workflow:

  1. Ensure that the required updates are uploaded and applied to the SystemController / central update repository.

    For more information, see Uploading and Applying Updates to SystemController Using Horizon <uploading-and-applying-updates-to-systemcontroller-using-horizon>.

  2. Create an update strategy for the update orchestration.

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

  3. Optionally, customize the configuration settings used by the update strategy.

    The update strategy is applied to the Central Cloud's RegionOne and all subclouds using default configuration settings. You can change these settings, and you can create custom settings for individual subclouds. For more information, see Customizing the Update Configuration for Distributed Cloud Update Orchestration <customizing-the-update-configuration-for-distributed-cloud-update-orchestration>.

  4. Apply the strategy for the update orchestration.

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

    As each subcloud is updated, it moves through the following states:

    initial

    The update has not started.

    updating patches

    Patches are being updated to synchronize with System Controller updates.

    creating strategy

    The strategy is being created in the subcloud.

    applying strategy

    The strategy is being applied in the subcloud.

    finishing

    updates that are no longer required are being deleted

    updates that require committing are being committed

    complete

    Updating has been completed successfully.

    During this process, alarms 900.001 and 900.101 are raised temporarily.

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

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>