7.2 Server Update Groups

Updates and upgrades to Oracle VM Servers can be performed using a server update repository. To access patch updates for Oracle VM, you should contact Oracle to purchase an Oracle VM Support contract and gain access to the Unbreakable Linux Network (ULN) which contains updates for Oracle VM. If you have access to ULN you can use this to set up your own server update repository to use when updating your Oracle VM Servers. Setting up a repository is beyond the scope of this documentation, however you can read about setting up a Yum repository for x86-based servers in an OTN article Yum Repository Setup at:

http://www.oracle.com/technetwork/articles/servers-storage-admin/yum-repo-setup-1659167.html

Make sure you subscribe to the Oracle VM Release 3.3 channel on ULN when you set up your Yum repository. For SPARC-based servers, you should refer to Upgrading Oracle VM Agent for SPARC in the Oracle VM Installation and Upgrade Guide for further information on configuring Oracle Solaris IPS repositories.

There are two server update groups, one for x86-based Oracle VM Servers, and one for SPARC-based Oracle VM Servers. You can create multiple repositories for each server update group, and enable repositories as required. These repositories are available to all Oracle VM Servers of that type, so all x86-based Oracle VM Servers can access all the server update repositories created in the x86 server update group.

To override either of these default repositories and create a repository that is restricted to a particular server pool, see Section 3.4.6, “Server Update Repositories Perspective”. To update an Oracle VM Server, see Section 3.4.2.10, “Update Server”.

If you have one or more server update repositories configured for Oracle VM Server updates, you add and manage these using the Server Update Groups subtab.

Important

If you have previously upgraded your Oracle VM Servers from a 3.2 release, as described in Upgrading Oracle VM Server for x86 in the Oracle VM Installation and Upgrade Guide the, you may still have the transitional repository enabled among your listed server update groups. This repository is named '3.3_trans_repo'. It is very important that once you have finished upgrading your servers from the 3.2 release you disable or remove this repository. If this repository is enabled and you perform an upgrade between errata releases, the upgrade may fail.

The Server Update Groups subtab provides facilities to add, edit and delete server update repositories. These options can be accessed using the toolbar at the top of the tab when you click on an item within the navigation tree or management pane table.

This subtab includes a toolbar that consists of the following options:

Table 7.3 Server Update Repository Subtab Toolbar Icon Options

Toolbar Icon Option

Icon

Description

Create New Server Update Repository...

Create New Server Update Repository... icon

Displays the Create Server Update Repository dialog box. Use this option to create a new server update repository.

Edit Server Update Repository...

Edit Server Update Repository... icon

Displays the Edit Server Update Repository dialog box. Use this option to edit an existing server update repository.

Delete Server Update Repository

Delete Server Update Repository icon

Displays the Delete Confirmation dialog box. Use this option to delete the selected server update repository.