|
|
-
Back up the CMAS cloudmanager database instance.
|
Section 20.1, Backing Up the PostgreSQL Database
|
|
|
-
(Optional) Back up the CMAS components, including custom files you might have created for it.
|
Section 20.2, Backing Up the Application Server Components and Custom Files
|
|
|
-
Install the upgrade package for Application Server.
|
Section 20.3, Install the Cloud Manager Package
|
|
|
-
Configure the updated Application Server.
|
Section 20.4, Running the Cloud Manager Configuration Script
|
|
|
-
Ensure that you understand the planning requirements for the CMOS upgrade.
|
Section 21.0, Orchestration Components Upgrade Overview
|
|
|
-
Back up the CMOS components.
|
Section 22.1, Backing Up Orchestration Components Prior to Upgrading
|
|
|
-
Check the current version of CMOS components running in your Cloud Manager system.
|
Section 22.2, Checking the Current Version of Cloud Manager Orchestration Components
|
|
|
-
Ensure that all running jobs are complete and take a snapshot of the current configuration of the Orchestration Server.
|
Section 22.3, Snapshotting the Existing Orchestration Server Installation
|
|
|
-
Install the upgrade packages for Orchestration components:
-
Orchestration Server
-
Orchestration Console
-
Orchestration Agent
-
Monitoring Server
-
Monitoring Agent
|
Section 22.4, Upgrading Orchestration Components
|
|
|
-
Configure the updated Orchestration components.
|
Section 22.5, Configuring the Upgraded Orchestration Components
|
|
|
-
Configure the remote audit database.
|
Section 22.6, Configuring the Remote Audit Database after Orchestration Components Are Upgraded
|
|
|
-
Run Discovery on VM Hosts and Images.
|
Section 22.7, Running Discovery on VM Hosts and Images
|
|
|
-
Update resource pool data on the Cloud Manager Application Server.
|
Section 20.5, Using the Configurator Tool to Update Resource Pool Data on the Cloud Manager Application Server
|