5.4.1.3 Configuring the Yum Repositories within Oracle VM Manager

The two required Yum repositories must be set up within the Oracle VM Manager Web Interface, so that the upgrade script can identify them accurately and use them to perform the upgrade on the specified Oracle VM Servers. The Yum repositories are called server update repositories in the Oracle VM Manager Web Interface.

Use the Oracle VM Manager Web Interface to create two server update repositories, one for each Yum repository. Make sure you create these server update repositories in the x86 server update group. The following tables contain the information you need to create the server update repositories using the Create Server Update Repository dialog box.

Full instructions for creating a server update repository using a Yum repository in the Oracle VM Manager Web Interface are provided in Create New Server Update Repository in the Oracle VM Manager User's Guide.

Table 5.1 Oracle VM Server 3.3 Transitional Update Repository

Field	Value	Notes
Name	`3.3_trans_repo`	By naming the repository in this way within Oracle VM Manager you are able to use the UpgradeServers.py script described in Section 5.4.2, “Upgrading Oracle VM Server using the UpgradeServers.py Script”. The name is case sensitive.
Repository Name	`3.3_trans_repo`
URL	`http://example.com/repos/Transition`	Substitute this URL with the URL to your repository.
Enabled	Yes	This repository must be enabled if you intend to use the UpgradeServers.py script described in Section 5.4.2, “Upgrading Oracle VM Server using the UpgradeServers.py Script”.
Package Signature Type	GPG or None	If you want to verify the validity of packages provided by the repositories, set the signature type to use a `GPG` key. Alternatively, use `NONE` if there is no verification required.
Package Signature Key	`http://example.com/repos/RPM-GPG-KEY-oracle-ol5`	If you opted to verify the validity of packages provided by the repository, provide the verification signature for the repository. Substitute this URL with the URL to the verification signature for the repository. Note that this should be the GPG key provided for the Oracle Linux 5 repository.

Table 5.2 Oracle VM Server 3.3 Update Repository

Field	Value	Notes
Name	`3.3_ovs_repo`	By naming the repository in this way within Oracle VM Manager you are able to use the UpgradeServers.py script described in Section 5.4.2, “Upgrading Oracle VM Server using the UpgradeServers.py Script”. The name is case sensitive.
Repository Name	`3.3_ovs_repo`
URL	`http://example.com/repos/Server`	Substitute this URL with the URL to your repository.
Enabled	Yes	This repository must be enabled if you intend to use the UpgradeServers.py script described in Section 5.4.2, “Upgrading Oracle VM Server using the UpgradeServers.py Script”.
Package Signature Type	GPG or None	If you want to verify the validity of packages provided by the repositories, set the signature type to use a `GPG` key. Alternatively, use `NONE` if there is no verification required.
Package Signature Key	`http://example.com/repos/RPM-GPG-KEY-oracle`	If you opted to verify the validity of packages provided by the repository, provide the verification signature for the repository. Substitute this URL with the URL to the verification signature for the repository. Note that this should be the GPG key provided for the Oracle Linux 6 repository.