ac4d8fea44
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
85 lines
2.8 KiB
ReStructuredText
85 lines
2.8 KiB
ReStructuredText
|
|
.. gjf1592841770001
|
|
.. _upgrade-management-overview:
|
|
|
|
===========================
|
|
Upgrade Management Overview
|
|
===========================
|
|
|
|
You can upgrade |prod|'s |prod-dc|'s System Controller, and subclouds with a new
|
|
release of |prod| software.
|
|
|
|
.. rubric:: |context|
|
|
|
|
.. note::
|
|
|
|
Backup all yaml files that are updated using the Redfish Platform
|
|
Management service. For more information, see :ref:`Installing a Subcloud
|
|
Using Redfish Platform Management Service
|
|
<installing-a-subcloud-using-redfish-platform-management-service>`.
|
|
|
|
You can use the |CLI| to manage upgrades. The workflow for upgrades is as
|
|
follows:
|
|
|
|
|
|
.. _upgrade-management-overview-ol-uqv-p24-3mb:
|
|
|
|
#. To upgrade the |prod-dc| system, you must first upgrade the
|
|
System Controller. See :ref:`Upgrading the System Controller Using the CLI
|
|
<upgrading-the-systemcontroller-using-the-cli>`.
|
|
|
|
#. Use |prod-dc| Upgrade Orchestration to upgrade the subclouds. See
|
|
:ref:`Distributed Upgrade Orchestration Process Using the CLI <distributed-upgrade-orchestration-process-using-the-cli>`.
|
|
|
|
#. To handle errors during an orchestrated upgrade, see :ref:`Error
|
|
Handling During An Orchestrated Upgrade
|
|
<robust-error-handling-during-an-orchestrated-upgrade>`.
|
|
|
|
.. rubric:: |prereq|
|
|
|
|
The following prerequisites apply to a |prod-dc| upgrade management service.
|
|
|
|
.. _upgrade-management-overview-ul-smx-y2m-cmb:
|
|
|
|
- **Configuration Verification**: Ensure that the following configurations
|
|
are verified before you proceed with the upgrade on the |prod-dc|
|
|
and subclouds:
|
|
|
|
|
|
- Run the :command:`system application-list` command to ensure that all
|
|
applications are running.
|
|
|
|
- Run the :command:`system host-list` command to list the configured
|
|
hosts.
|
|
|
|
- Run the :command:`dcmanager subcloud list` command to list the
|
|
subclouds.
|
|
|
|
- Run the :command:`kubectl get pods --all-namespaces` command to test
|
|
that the authentication token validates correctly.
|
|
|
|
- Run the :command:`fm alarm-list` command to check the system health to
|
|
ensure that there are no unexpected or management-affecting alarms.
|
|
|
|
- Run the :command:`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 |AIO-DX|, and using the Redfish
|
|
platform management service.
|
|
|
|
- **Remove Non GA Applications**:
|
|
|
|
- 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.
|
|
|
|
|
|
.. only:: partner
|
|
|
|
.. include:: ../_includes/upgrade-management-overview.rest
|