docs/doc/source/dist_cloud/upgrade-management-overview.rst
Adil ac4d8fea44 Node Management and Distributed cloud Guide updates
Global Pass Upgrades

Added content from emails attached to ticket and sharepoint

Pacth 01: inputs from email by Greg

Patch 03: Created new section for subcloud group
          updated table 1 shared system configurations

Patch 04: corrected typos (Mary's comments)

Patch 05: solved merged conflict

patch 06: removed broken link

Story: TBD
Task: TBD



Signed-off-by: Adil <mohamed.adilassakkali@windriver.com>
Change-Id: I60b0a40a60a44d30429cd3a4dd8374c16345951a
2021-05-27 16:31:17 -03:00

2.8 KiB

Upgrade Management Overview

You can upgrade 's 's System Controller, and subclouds with a new release of software.

Note

Backup all yaml files that are updated using the Redfish Platform Management service. For more information, see Installing a Subcloud Using Redfish Platform Management Service <installing-a-subcloud-using-redfish-platform-management-service>.

You can use the to manage upgrades. The workflow for upgrades is as follows:

  1. To upgrade the system, you must first upgrade the System Controller. See Upgrading the System Controller Using the CLI <upgrading-the-systemcontroller-using-the-cli>.
  2. Use Upgrade Orchestration to upgrade the subclouds. See Distributed Upgrade Orchestration Process Using the CLI <distributed-upgrade-orchestration-process-using-the-cli>.
  3. To handle errors during an orchestrated upgrade, see Error Handling During An Orchestrated Upgrade <robust-error-handling-during-an-orchestrated-upgrade>.

The following prerequisites apply to a upgrade management service.

  • Configuration Verification: Ensure that the following configurations are verified before you proceed with the upgrade on the and subclouds:
    • Run the system application-list command to ensure that all applications are running.
    • Run the system host-list command to list the configured hosts.
    • Run the dcmanager subcloud list command to list the subclouds.
    • Run the kubectl get pods --all-namespaces command to test that the authentication token validates correctly.
    • Run the fm alarm-list command to check the system health to ensure that there are no unexpected or management-affecting alarms.
    • Run the kubectl get host -n deployment command to ensure all nodes in the cluster have reconciled and is set to 'true'.
    • Ensure controller-0 is the active controller.
  • The subclouds must all be , and using the Redfish platform management service.
  • Remove Non GA Applications:
    • Use the system application-remove and system application-delete commands to remove the application on the subclouds.
    • Remove any non-GA applications and -openstack, from the system, if they exist.

partner