Some releases of the Oracle PCA 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.
Oracle PCA 2.3.x and Oracle VM 3.4.x
Release 2.3.x of the Oracle PCA Controller Software is a milestone release, bringing all the improvements of Oracle VM 3.4.x to Oracle Private Cloud Appliance. The differences with Oracle VM 3.2.x are so significant that additional prerequisites must be met before the update can proceed. As a consequence, the upgrade of the compute nodes to the new version of Oracle VM Server also requires a different approach.
Both compute node upgrade procedures are described in separate sections below. Make sure that you follow the correct procedure for your Oracle PCA environment.
If you are installing Oracle Private Cloud Appliance Controller Software Release 2.3.x, then the management nodes are set up to run Oracle VM Manager 3.4.x.
Compute nodes cannot be upgraded to Oracle VM Server Release 3.4.x with the Oracle VM Manager web UI. You must upgrade them using the update compute-node command within the Oracle PCA CLI.
With Oracle PCA Controller Software up to Release 2.3.3, if
you do attempt to upgrade a compute node from within
Oracle VM Manager, the resulting error message provides false
information. Do not use the suggested
UpgradeServers.py script but use the
Oracle PCA CLI as described in this section. As of Release
2.3.4, the script in question no longer applies, since all
compute nodes must already be running Oracle VM Server Release
3.4.x.
After the Oracle VM Manager upgrade to Release 3.4.x, an event is generated for each compute node because the Oracle VM Server version is "older than the management version". This is expected behavior and the events are cleared when the compute nodes have been upgraded to Release 3.4.x.
With Oracle PCA Controller Software up to Release 2.3.3, it is possible to keep part of your environment running at Oracle VM Server Release 3.2.10 or 3.2.11, but those compute nodes can no longer be reconfigured with Oracle VM Manager Release 3.4.x. For more information about the functional restrictions, see Section 8.10, “Managing a Mixed Compute Node Environment”. As of Oracle PCA Controller Software Release 2.3.4, this note no longer applies, since all compute nodes must already be running Oracle VM Server Release 3.4.x.
Upgrading a Compute Node to a Newer Oracle VM Server Release
Execute this procedure on each compute node after the software update on the management nodes has completed successfully.
If compute nodes are running other packages that are not part of Oracle PCA, such as external storage plugins from other vendors, these must be uninstalled before the Oracle VM Server upgrade. For details, see Third-Party Oracle Storage Connect Plugins Must Be Removed Before Appliance Software Update to Release 2.3.1 in the Oracle Private Cloud Appliance Release Notes.
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 PCA CLI:
# pca-admin Welcome to PCA! Release: 2.3.3 PCA> show version ---------------------------------------- Version 2.3.3 Build 999 Date 2018-01-17 ---------------------------------------- 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”.
Identify the master server in each server pool.
NoteIf the Oracle PCA was previously updated with controller software Release 2.3.1 or newer, and the compute nodes have already been upgraded to Oracle VM Server 3.4, then there is no master server. You can skip this step and upgrade the compute nodes in any order.
In the Servers and VMs tab, select the server pool in the navigation pane.
In the management pane, select the Info perspective from the list in the toolbar.
A configuration overview of the server pool is displayed.
As long as the compute nodes in the server pool are running Oracle VM Server 3.2.x, one of them is a master server. Locate the Master Server setting and write down which server is the pool master.
CautionThe server pool master server should be the last Oracle VM Server to go through this upgrade procedure. This allows you to upgrade the compute nodes one by one without causing the master role to be transferred to another node in the server pool each time. This eliminates potential resource locks and errors related to transferring the master role, and saves a significant amount of time.
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.
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.
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.
Return to the open management node console window with active CLI connection.
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.
WarningRunning 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 upgrade. It also ensures that all the necessary packages are installed from the correct source location, and configured properly.
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.
WarningIf 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.
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.
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 PCA.
CautionThe server pool master server should be the last Oracle VM Server in a pool to go through this upgrade procedure. This allows you to upgrade the compute nodes one by one without causing the master role to be transferred to another node in the server pool each time. This eliminates potential resource locks and errors related to transferring the master role, and saves a significant amount of time.
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 PCA is ready to resume all normal operations.
If you are installing Oracle Private Cloud Appliance Controller Software Release 2.3.x, please follow the instructions in Section 3.5.1, “Oracle PCA 2.3 – Upgrading Oracle VM to Release 3.4” instead.
If you are installing Oracle Private Cloud Appliance Controller Software Release 2.2.x or earlier, then the Oracle VM Manager version on the management nodes may have been upgraded to a newer version 3.2.x. To check which Oracle PCA Controller Software Releases include an Oracle VM upgrade, refer to Section 3.2, “Mandatory Updates”. If this is the case for your controller software, then the compute nodes should be upgraded to the corresponding version of Oracle VM Server. Follow the procedure in this section to perform the upgrade.
Upgrading a Compute Node to a Newer Version of Oracle VM Server 3.2
Execute this procedure on each compute node after the software update on the management nodes has completed successfully. At that stage, the YUM repository configuration of all compute nodes has been updated to point to the new Oracle VM Server packages on the Oracle PCA internal storage.
A large part of this procedure must be executed from Oracle VM Manager. An overview of its usage in the context of Oracle PCA, and links to detailed instructions in the Oracle VM documentation, are provided in this Administrator's Guide, in Chapter 5, Managing the Oracle VM Virtual Infrastructure.
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 PCA CLI:
# pca-admin Welcome to PCA! Release: 2.2.1 PCA> show version ---------------------------------------- Version 2.2.1 Build 999 Date 2016-05-17 ---------------------------------------- Status: Success
Log in to Oracle VM Manager.
For details, see Section 5.2, “Logging in to the Oracle VM Manager Web UI”.
Identify the master server in the server pool.
In the Servers and VMs tab, select the server pool in the navigation pane.
In the management pane, select the Info perspective from the list in the toolbar.
A configuration overview of the server pool is displayed.
Locate the Master Server setting and write down which server is the pool master.
CautionThe server pool master server should be the last Oracle VM Server to go through this upgrade procedure. This allows you to upgrade the compute nodes one by one without causing the master role to be transferred to another node in the server pool each time. This eliminates potential resource locks and errors related to transferring the master role, and saves a significant amount of time.
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 maintenance mode is provided in the Oracle VM Manager User's Guide section entitled Edit Server.
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.
Select the 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 on the compute node in question.
Information on the Oracle VM Server update functionality is provided in the Oracle VM Manager User's Guide section entitled Update Server.
In the Servers and VMs tab, select the server pool in the navigation pane.
In the management pane, select the Servers perspective from the list in the toolbar.
A table is displayed with all servers in the server pool.
Select the appropriate compute node in the management pane table and click Update Server in the management pane toolbar.
As part of the update procedure, the Oracle VM Server is restarted but remains in maintenance mode.
WarningIf the compute node does not reboot during the update, you must restart it from within Oracle VM Manager.
Take the compute node out of maintenance mode.
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.
Clear the 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 PCA.
CautionThe server pool master server should be the last Oracle VM Server to go through this upgrade procedure. This allows you to upgrade the compute nodes one by one without causing the master role to be transferred to another node in the server pool each time. This eliminates potential resource locks and errors related to transferring the master role, and saves a significant amount of time.
The appliance software update is now complete. The Oracle PCA is ready to resume all normal operations.