7.3 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.4 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, you should disable or remove the transitional Yum repository when you successfully complete the Oracle VM Server upgrade process. Disabling or removing the transitional Yum repository is a best practice as it is no longer required after the upgrade process.

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.

Help

Help icon

Displays context sensitive help.


7.3.1 Create New Server Update Repository

To create a new server update repository:

  1. Click the Reports and Resources tab.

  2. Click the Server Update Groups subtab.

  3. In the navigation tree, select GlobalSparcServerUpdateConfiguration to create a repository for SPARC-based Oracle VM Servers, or GlobalX86ServerUpdateConfiguration for x86-based Oracle VM Servers.

  4. Click Create New Server Update Repository Create New Server Update Repository to display the Create Server Update Repository dialog box. Enter the following information about the repository:

    • Name: A name for the repository as stored in Oracle VM Manager.

    • Repository Name: The repository name as used by a server to distinguish between different upgrade repositories. This may only contain alphanumeric characters and underscores. No spaces are permitted. For SPARC environments, the repository name must match a valid publisher at the URL where the repository is hosted.

    • URL: The URL to access the repository, for example:

      http://example.com/OVM3/Server/
      Note

      The URL should contain the RPMs and the repodata directory created by the createrepo tool. If you are copying the RPMs from the Oracle VM Server ISO media, or loop mounting the ISO file, make sure to include the Server directory (which includes the repodata directory), for example:

      http://example.com/OVM3/Server/

    • Enable: Whether to enable the repository.

    • Package Signature Type: The signature type to verify the validity of the repository, either GPG key, CA (Certificate Authority). Use NONE if there is no verification required.

    • Package Signature Key: The verification signature for the repository, for example, the location of the GPG key:

      http://example.com/OVM3/RPM-GPG-KEY

      The GPG key must be available via one of HTTP, FTP, FILE or HTTPS protocols.

      The GPG key for Oracle-signed updates from ULN is pre-installed on Oracle VM Server at /etc/pki/rpm-gpg/RPM-GPG-KEY-oracle. If you want to use this GPG key, enter:

      file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle

      The value for this field is required if you select a Package Signature Type other than NONE.

    • Description: An optional description for the repository.

    Click OK.

The repository is added and ready to use to update Oracle VM Servers for the server update group. Note that if repository creation fails for a particular server, then an event is generated on the affected server. Oracle VM Manager does not attempt to validate the repository before it is added to each server. If the repository is invalid or, in the case of a SPARC repository, the repository name does not match a valid publisher at the URL specified, an error event is generated for the servers affected.

The repository is checked regularly for updates by the Server Upgrade Checker Task recurring job, though there may be a delay between the repository being created and the update notification being displayed in Oracle VM Manager. To change the frequency of the Server Upgrade Checker Task recurring job, see Section 8.2, “Recurring”.

7.3.2 Edit Server Update Repository

To edit a server update repository:

  1. Click the Tools and Resources tab.

  2. Click the Server Update Groups subtab.

  3. In the navigation tree, select GlobalSparcServerUpdateConfiguration to edit a repository for SPARC-based Oracle VM Servers, or GlobalX86ServerUpdateConfiguration for x86-based Oracle VM Servers.

  4. Select a repository from the table in the management pane.

  5. Click Edit Server Update Repository Edit Server Update Repository icon to display the Edit Server Update Repository dialog box. Edit the fields as described in Section 7.3.1, “Create New Server Update Repository”. Click OK.

7.3.3 Delete Server Update Repository

To delete a server update repository:

  1. Click the Tools and Resources tab.

  2. Click the Server Update Groups subtab.

  3. In the navigation tree, select GlobalSparcServerUpdateConfiguration to delete a repository for SPARC-based Oracle VM Servers, or GlobalX86ServerUpdateConfiguration for x86-based Oracle VM Servers.

  4. Select a repository from the table in the management pane.

  5. Click Delete Server Update Repository Delete Server Update Repository icon .

  6. A confirmation dialog is displayed. Click OK to delete the repository.