Distributed Cloud Upgrades

Added new content to DC guide

List of impacted topics:

       -Upgrade Management Overview
       -Upgrading the SystemController Using the CLI
       -Distributed Upgrade Orchestration Process Using the CLI
       -Robust Error Handling During An Orchestrated Upgrade
       -Failure Prior to the installation of N+1 Load on a Subcloud
       -Failure During the Installation or Data Migration of N+1 Load on a Subcloud
          - Removed section-> Failure Caused by Invalid Docker Registry Certificate


Story: TBD
Task: TBD


Signed-off-by: Adil <mohamed.adilassakkali@windriver.com>
Change-Id: I8538dd6bda8651d76964f64c250df627bace75cb
This commit is contained in:
Adil
2021-05-31 13:20:24 -03:00
committed by Mohamed Adil Assakkali
parent 5b39d5781a
commit cfa6850d84
3 changed files with 7 additions and 9 deletions

View File

@@ -6,9 +6,8 @@
Distributed Upgrade Orchestration Process Using the CLI
=======================================================
Distributed upgrade orchestration can be initiated after the upgrade and
stability of the System Controller cloud. Distributed upgrade orchestration can
be initiated after the system controller has been successfully upgraded.
Distributed upgrade orchestration can be initiated after the System Controller
has been successfully upgraded.
.. rubric:: |context|
@@ -26,7 +25,7 @@ using parameters to specify:
Based on these parameters, and the state of the subclouds, the upgrade
orchestrator creates a number of stages for the overall upgrade strategy. All
orchestration creates a number of stages for the overall upgrade strategy. All
the subclouds that are included in the same stage will be upgraded in parallel.
.. rubric:: |prereq|

View File

@@ -21,7 +21,7 @@ Errors can occur due to one of the following:
- One or more invalid install values
- A network error that results in the subcloud's being temporarily unreachable
- A network error that results in the subcloud being temporarily unreachable
**Failure Caused by Install Values**

View File

@@ -73,11 +73,10 @@ The following prerequisites apply to a |prod-dc| upgrade management service.
- Use the :command:`system application-remove` and :command:`system
application-delete` commands to remove the application on the
subclouds.
- Remove any non-GA applications and
|prefix|-openstack, from the |prod-dc| system, if they exist.
subclouds:
- Remove any non-GA and |prefix|-openstack applications, from the
|prod-dc| system, if they exist.
.. only:: partner