3.3 Upgrading the Virtualization Platform

Some releases of the Oracle Private Cloud Appliance Controller Software include a new version of Oracle VM, the virtualization platform used in Oracle Private Cloud Appliance. As part of the controller software update, the new Oracle VM Manager Release is automatically installed on both management nodes.

After the controller software update on the management nodes, Oracle VM Manager displays events indicating that the compute nodes are running outdated version of Oracle VM Server. These events are informational and do not prevent any operations, but it is recommended that you upgrade all compute nodes to the new Oracle VM Server Release at your earliest convenience.

The Oracle VM Server upgrade was intentionally decoupled from the automated controller software update process. This allows you to plan the compute node upgrades and the migration or downtime of your virtual machines in steps and outside peak hours. As a result, service interruptions for users of the Oracle VM environment can be minimized or even eliminated. By following the instructions in this section, you also make sure that previously deployed virtual machines remain fully functional when the appliance update to the new software release is complete.

During an upgrade of Oracle VM Server, no virtual machine can be running on a given compute node. VMs using resources on a shared storage repository can be migrated to other running compute nodes. If a VM uses resources local to the compute node you want to upgrade, it must be shut down, and returned to service after the Oracle VM Server upgrade.

When you install Oracle Private Cloud Appliance Controller Software Release 2.4.x, the management nodes are set up to run Oracle VM Manager 3.4.x. Compute nodes cannot be upgraded to the corresponding Oracle VM Server Release with the Oracle VM Manager web UI. You must upgrade them using the update compute-node command within the Oracle Private Cloud Appliance CLI.

Upgrading a Compute Node to a Newer Oracle VM Server Release

Caution

Execute this procedure on each compute node after the software update on the management nodes has completed successfully.

Caution

If compute nodes are running other packages that are not part of Oracle Private Cloud Appliance, these must be uninstalled before the Oracle VM Server upgrade.

Make sure that the appliance software has been updated successfully to the new release.
You can verify this by logging into the master management node and entering the following command in the Oracle Private Cloud Appliance CLI:
```
# pca-admin
Welcome to PCA! Release: 2.4.2
PCA> show version

----------------------------------------
Version              2.4.2
Build                000
Date                 2019-10-10
----------------------------------------

Status: Success
```
Leave the console and CLI connection open. You need to run the update command later in this procedure.
Log in to Oracle VM Manager.
For details, see Section 5.2, “Logging in to the Oracle VM Manager Web UI”.
Migrate all running virtual machines away from the compute node you want to upgrade.
Information on migrating virtual machines is provided in the Oracle VM Manager User's Guide section entitled Migrate or Move Virtual Machines.
Place the compute node in maintenance mode.
Information on using maintenance mode is provided in the Oracle VM Manager User's Guide section entitled Edit Server.
1. In the Servers and VMs tab, select the Oracle VM Server in the navigation pane. Click Edit Server in the management pane toolbar.
  The Edit Server dialog box is displayed.
2. Select the Server in Maintenance Mode check box to place the Oracle VM Server into maintenance mode. Click OK.
  The Oracle VM Server is in maintenance mode and ready for servicing.
Run the Oracle VM Server update for the compute node in question.
1. Return to the open management node console window with active CLI connection.
2. Run the update compute-node command for the compute nodes you wish to update at this time. Run this command for one compute node at a time.
  Warning
  Running the update compute-node command with multiple servers as arguments is not supported. Neither is running the command concurrently in separate terminal windows.
```
PCA> update compute-node ovcacn09r1
************************************************************
 WARNING !!! THIS IS A DESTRUCTIVE OPERATION.
************************************************************
Are you sure [y/N]:y

Status: Success
```
  This CLI command invokes a validation mechanism, which verifies critical requirements that a compute node must meet to qualify for the Oracle VM Server 3.4.x upgrade. It also ensures that all the necessary packages are installed from the correct source location, and configured properly.
3. Wait for the command to complete successfully. The update takes approximately 30 minutes for each compute node.
  As part of the update procedure, the Oracle VM Server is restarted but remains in maintenance mode.
  Warning
  If the compute node does not reboot during the update, you must restart it from within Oracle VM Manager.
Return to Oracle VM Manager to take the compute node out of maintenance mode.
1. In the Servers and VMs tab, select the Oracle VM Server in the navigation pane. Click Edit Server in the management pane toolbar.
  The Edit Server dialog box is displayed.
2. Clear the Server in Maintenance Mode check box. Click OK.
  The Oracle VM Server rejoins the server pool as a fully functioning member.
Repeat this procedure for each compute node in your Oracle Private Cloud Appliance.

The appliance software update is now complete. Next, perform the required post-upgrade verification steps. The procedure for those additional manual verification tasks is documented in the Post Upgrade section of the support note with Doc ID 2242177.1.

After successful completion of the post-upgrade verification steps, the Oracle Private Cloud Appliance is ready to resume all normal operations.