starlingx/docs
Code Issues Proposed changes
docs/doc/source/dist_cloud/kubernetes/upgrade-management-overview.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.1 KiB
Raw Blame History

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

For subclouds, end user container images in `registry.local` will be backed up during the upgrade process. This only includes images other than system and application images. These images are limited to 5 GBytes in total size. If the system contains more than 5 GBytes of these images, the upgrade start will fail.

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 must use 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 and -openstack applications, from the system, if they exist.

partner