2.5 Update

2.5 Update
Prev	Chapter 2 Monitoring and Managing Oracle Virtual Compute Appliance	Next

Updates of the Oracle Virtual Compute Appliance are performed from the command line of the master management node. Software updates are a three-tier process. First, a zipped ISO containing the updated software must be downloaded from MOS and made available on an HTTP or FTP server. From there, the ISO is downloaded to the ZFS storage appliance. When the download is complete and the software is unpacked in the appropriate directories, the update is activated and applied to each affected component.

Caution

If direct public access is not available within your data center and you make use of proxy servers to facilitate HTTP, HTTPS and FTP traffic, it may be necessary to edit /etc/ovca.conf, on each management node, to ensure that the correct proxy settings are specified for a download to succeed from the Internet. This depends on the network location from where the download is served. See Section 6.1, “Adding Proxy Settings for Oracle Virtual Compute Appliance Updates” for more information.

Tip

Updates are controlled with ovca-updater commands. To display usage options, enter ovca-updater --help at the shell prompt of the management node.

Updating the Oracle Virtual Compute Appliance Software

Log into My Oracle Support and download the required Oracle Virtual Compute Appliance software update.
You can find the update by searching for the product name “Oracle Virtual Compute Appliance”, or for the Patch or Bug Number associated with the update you need.
Make the update, a zipped ISO, available on an HTTP or FTP server that is reachable from your Oracle Virtual Compute Appliance.
Using SSH and an account with superuser privileges, log into the management node.
Note
The default root password is Welcome1.
Connect to the management node using its IP address in the data center network, as you configured it in the Network Setup tab of the Oracle Virtual Compute Appliance Dashboard. For details, see Section 2.4, “Network Setup”.
Note
The data center IP address used in this procedure is an example.
```
# ssh root@10.100.1.101
root@10.100.1.101's password:
root@ovcamn05r1 ~]#
```

Download the ISO to your Oracle Virtual Compute Appliance.

# ovca-updater -m download -s -u http://download-url.example.com/ovca-version-build.iso.zip
Download of http://download-url.example.com/ovca-version-build.iso.zip started successfully. \
Task id is 5ba4f1a09c9546b29a560e3d6682ce67

Check the progress of the ISO download. When the download is finished, proceed with the next step.

# ovca-updater -m download -l -i 5ba4f1a09c9546b29a560e3d6682ce67
Task ID                           Pct   Elapsed time Status
5ba4f1a09c9546b29a560e3d6682ce67  60%   155.305 sec    RUNNING 
# ovca-updater -m download -l -i 5ba4f1a09c9546b29a560e3d6682ce67
Task ID                           Pct   Elapsed time Status
5ba4f1a09c9546b29a560e3d6682ce67  70%   285.904 sec    RUNNING 
# ovca-updater -m download -l -i 5ba4f1a09c9546b29a560e3d6682ce67
Task ID                           Pct   Elapsed time Status
5ba4f1a09c9546b29a560e3d6682ce67 100%   338.102 sec    SUCCESS

To list all downloads and their status, enter this command:

# ovca-updater -m download -l
Task ID                           Pct   Elapsed time Status
5ba4f1a09c9546b29a560e3d6682ce67 100%   338.102 sec    SUCCESS

When the download has completed successfully, activate it by launching the update process.
```
# ovca-updater -m update -s
WARNING:root:Activating update process. Starting with nonmaster node 192.168.4.4
```
Once you issue this command, the update process is initiated as described in Section 1.7, “Oracle Virtual Compute Appliance Software Update”.
Check the progress of the software update.
```
# ovca-updater -m update -l
Mgmt Node IP    Update Started      Update Ended        Elapsed
192.168.4.4     2013-10-02 16:52:14 ------------------- 0:02:18 
```
Note
At a certain point during the update process, the active management node is rebooted. As a result, the SSH connection is lost. In addition, this may cause the Dashboard to become unresponsive temporarily, and you may be required to log back in.
When the master management node reboots, the secondary (updated) management node assumes the master role. The original master management node is then also updated and becomes the backup management node.

Warning

When updating the Oracle Virtual Compute Appliance software stack from Release 1.0.2 to Release 1.1.1, you must verify that the specific Oracle VM Manager tuning has been applied properly. If Oracle VM Manager is using default settings instead, you must re-apply the tuning settings by running a script on the master management node. For step-by-step instructions, refer to Section 6.4, “Verifying and Re-applying Oracle VM Manager Tuning after Software Update”.

Warning

When updating the Oracle Virtual Compute Appliance software stack from Release 1.0.2 to Release 1.1.1, you must perform a critical upgrade procedure on each compute node that was originally provisioned with Release 1.0.2 software. The extra procedure is designed to correct the storage and clustered server pool configuration used by the compute nodes, while keeping the hosted virtual machines intact. For step-by-step instructions, refer to Section 6.5, “Upgrading Existing Compute Node Configuration to Release 1.1.1”.

Prev	Up	Next
2.4 Network Setup	Home	Chapter 3 Managing the Oracle VM Virtual Infrastructure