by Simon Coter with contributions from Christophe Pauliat, Olivier Canonge, and Doan Nguyen
Published December 2013
This hands-on lab takes you through the best practices for migrating an existing Oracle Database workload from VMware to Oracle VM. It also walks you through how to migrate to Oracle Linux a Red Hat Enterprise Linux 6 guest exported from VMware by downloading Oracle's Unbreakable Enterprise Kernel from Oracle's public yum server.
This document details all actions that were done during Oracle OpenWorld 2013 session Hands-On Lab 9981.
This hands-on lab takes you through the best practices for migrating an existing Oracle Database workload from VMware to Oracle VM. It also walks you through how to migrate to Oracle Linux a Red Hat Enterprise Linux 6 guest exported from VMware by downloading Oracle's Unbreakable Enterprise Kernel from Oracle's public yum server.
Oracle VM is a free-license product, and it's the only virtualization x86 software solution certified for all Oracle products.
This lab showcases the https://en.wikipedia.org/wiki/Open_Virtualization_Format (OVA) format, a free-of-charge service supplied by Oracle's public yum server with which Oracle Linux and Oracle VM can be maintained without a subscription. By performing the steps in this lab, you will obtain a fully supported and certified configuration for Oracle Database (whereas on VMware, Oracle Database is only supported, not certified).
During this lab at Oracle OpenWorld, we used a demo environment built on a single x86 laptop (using Oracle VM VirtualBox), which contained two virtual servers and one Oracle VM Server guest:
Note: You can also run this lab at your home or office on an x86 server, desktop, or laptop.
To save time and fit in the one-hour slot of Oracle OpenWorld labs, the following actions were performed before the actual lab.
Note: To run this lab from your home or office, perform the tasks in Appendix A first to prepare your environment before you run the lab.
In this lab, you will execute the following steps in Oracle Enterprise Manager Cloud Control 12c:
Note: The migration approach followed by this lab is not the only one; other valid migration methods are based on official Oracle VM Templates such as Oracle VM Templates for Oracle Database.
Figure 1 shows all the components (Oracle VM VirtualBox and Oracle VM virtual machines) with their names and configuration (memory, IP addresses, and so on).
Figure 1. Diagram of all the components and their configuration.
As previously explained, we will use Oracle VM VirtualBox to host the two servers (Oracle VM Server and Oracle VM Manager) on a single x86 physical machine.
In the console, you should see the two VMs we will use in this lab.
Figure 2. Oracle VM VirtualBox console.
desktop started
prompt on the hol9981_ovm_mgr VM console.https://192.168.56.100:7002/ovm/console
.
Note: Firefox might raise a security warning (for example, This Connection is Untrusted
) since the SSL certificates are self-signed. If so, ignore the warning (expand I understand the Risks, then click Add Exception, and then click Confirm Security Exception).
You should get the login window shown in Figure 3:
Figure 3. Login window.
Figure 4. Status of the Oracle VM pool and server in the Servers and VMs tab.
Figure 5. Networking tab.
Figure 6. Newly created VNICs.
Figure 7. Displaying the physical disks.
Figure 8. Selecting a physical disk.
Figure 9. Showing all repositories.
Figure 10. Editing a repository.
Figure 11. Selecting the Taken Ownership option.
Figure 12. Selecting the Present/Unpresent icon.
Figure 13. Presenting the repository to the server pool.
Figure 14. Refreshing the repository.
Figure 15. Refreshing the VM assembly.
The purpose of this section is to show how to import into Oracle VM an assembly that was exported from VMware as described in Appendix A. An assembly can be described as a template of a group of virtual machines or a collection of multiple VM templates.
Note for importing assemblies or templates into Oracle VM: Oracle VM assemblies or templates can be imported from an HTTP or FTP server. An HTTP server is shown in the following example.
Figure 16. Preparing to import an assembly.
.ova
file you exported from VMware earlier:
Example URL for a .ova
file stored on your own web server:
http://apachehost/path/file.ova
Example URL for a .ova
file stored on the Oracle VM Manager server:
http://192.168.56.100/ovas/rhel-64-oracle-rdbms.ova
Figure 17. Example of specifying the assembly location.
Figure 18. Following the progress of the import.
At the end of the job, your assembly will be shown in the Repositories tab with the same name as the .ova
file that was imported:
Figure 19. The imported assembly.
The purpose of this section is to show how-to create an Oracle VM Template starting from an assembly.
In Oracle VM Manager, templates and assemblies appear in different folders of the storage repository, but their VM configuration files and disk images are stored in the same location as those of other virtual machines and templates.
The procedure to obtain a new virtual guest starting from an assembly is:
Assembly =>Template =>New Guest(s)
To create the template based on the rhel-64-oracle-rdbms.ova
assembly exported from VMware, proceed with the following steps:
Figure 20. Preparing to create a template.
In our example, we use the following:
VM Template Name: rhel-64-oracle-rdbms
Description: Red Hat 6.4 x86-64 exported from VMware with Oracle Database on board
Figure 21. Specifying a name and description for the template.
Figure 22. Following the progress of the template creation.
Note: The creation of a VM template could take several minutes. The larger the size of the machine exported from VMware, the more time it will take to obtain the template. While waiting, read the next steps.
Click the Repositories tab, expand the repo01 repository, and select the VM Templates directory; after that, click the template and expand it.
Figure 23. Expanding the template.
The Oracle VM Template configuration should look like Figure 24:
Figure 24. Checking the template configuration.
The template, which was derived from an assembly exported from VMware, needs correct sizing and network configuration; so this section shows how to edit an Oracle VM Template.
Figure 25. Preparing to edit the template.
In the Configuration tab:
Operating System: Red Hat Enterprise Linux 6
Domain Type: Xen PVM
Max. Memory (MB): 2048
Memory (MB): 2048
Figure 26. Specifying the template configuration.
In the Networks tab:
Select 192.168.56.0 and move it to the Selected Ethernet Networks panel on the right using .
Figure 27. Selecting a network.
No changes need to be made in the Disks and Boot Order tabs, so click OK.
The result of this configuration is shown in Figure 28 and Figure 29:
Figure 28. Template configuration.
Figure 29. Network selection.
We will now create a guest (virtual machine) based on the template just created. This section will show how to create a guest from an Oracle VM Template (in our case, the Oracle VM Template has been derived from a virtual machine exported from VMware).
Figure 30. Preparing to create a virtual machine.
Clone count: 1
Repository: repo01
VM Template: rhel-64-oracle-rdbms
VM Name: vmdb01.oow.local
Server Pool: ovm-pool.oow.local
Description: first guest created from a VMware OVA
Figure 31. Specifying the virtual machine configuration.
Then click Finish to confirm the guest creation.
Figure 32. Verifying that the job completed successfully.
Note about Immediate VM creation on Oracle Cluster File System 2: The VM creation should be almost immediate since the repository uses the Oracle Cluster File System 2 file system and the reflink feature. This avoids the need to copy all blocks of the template files, but instead uses pointers to existing blocks in the new files. (For details on the Oracle Cluster File System 2 reflink feature, see https://blogs.oracle.com/wim/entry/ocfs2_reflink.)
Our guest is ready but, before we start it, we need to verify that everything was accomplished. This section will show how to verify a guest and start it.
Figure 33. Expanding the server pool.
Figure 34. Selecting the server.
Figure 35. Selecting the guest.
In the Configuration tab:
Name: vmdb01.oow.local
Operating System: Red Hat Enterprise Linux 6
Domain Type: Xen PVM
Max. Memory (MB): 2048
Memory (MB): 2048
Max. Processors: 1
Processors: 1
Priority: 50
Processor Cap %: 100
Figure 36. Verifying the guest configuration.
In the Networks tab:
Network: 192.168.56.0
Figure 37. Verifying the network configuration.
In the Disks tab:
For Slot 0, the Disk Type is Virtual Disk (no change).
For Slot 1, the Disk Type is Empty (changed from CD/DVD to Empty).
Figure 38. Verifying the disk configuration.
Click OK.
Figure 39. Starting the guest.
The guest will temporarily change to the "Starting" state; you can also verify that the job completed successfully. If you want, you can also click Job Details to see a detailed log of the start process.
Figure 40. Getting details for the job.
Figure 41. Verifying that the job completed successfully.
Obviously this guest needs some changes. First of all, the network configuration needs to be changed since the default network configuration on VMware is network 192.168.93.0/24 while the default network configuration on Oracle VM VirtualBox is 192.168.56.0/24.
Also, guest ovmdb01.oow.local is not network-reachable, so you have to connect to its console to modify the network configuration; this section will show how to open a guest console and modify a network configuration.
Figure 42. Opening a guest console.
Figure 43. Pop-up blocker message.
ovm_rasproty-ws.jnlp
); choose Open with and select /usr/java/latest/bin/javaws (the latest installed JRE on your machine).
Figure 44. Confirming that the file should be opened.
Figure 45. Telling the browser to open the file using the JRE.
Click OK to confirm.
The console with a boot-progress bar will appear but it will not have a login prompt:
Figure 46. Console without login prompt.
Figure 47. Selecting the ALT option.
IMPORTANT: This task might not be possible from your home or office if no local VNC client is installed. If you aren't able to get the login prompt on the console, use the substeps below to determine the DHCP address assigned to the Red Hat Enterprise Linux 6 guest (vmdb01.oow.local) and then connect to the guest. If you are able to get the login prompt, proceed to Step 5.
ssh root@192.168.56.100
(the root password is ovsroot
).tail-50 /var/log/messages |grep DHCPACK
, for example:
[root@ovm-mgr ~]# tail -50 /var/log/messages |grep DHCPACK
Aug 16 01:59:30 ovm-mgr dhcpd: DHCPACK on 192.168.56.254 to 00:21:f6:00:00:02 via eth0
ovsroot
), for example:
ssh root@192.168.56.254
Figure 48. Login prompt.
Log in using the following:
User: root
Password: ovsroot
#vmware-uninstall-tools.pl
Figure 49. Uninstalling the VMware tools.
Figure 50. Verifying the uninstallation of the VMware tools.
#ifconfig eth0
Figure 51. Verifying the guest IP address.
#ssh root@<IP_address_obtained>
Note: The guest root password is ovsroot
.
Figure 52. Connecting to the guest.
# service oraOOWDB status
# ps -edaf |grep oracle
The output should be similar to Figure 53:
Figure 53. Verifying the status of Oracle Database and Oracle Listener.
One of the goals of this lab is to show Oracle's public yum server: http://public-yum.oracle.com.
Oracle's public yum server offers a free and convenient way to install the latest Oracle Linux packages as well as packages from the Oracle VM installation media via a yum client.
You can download the full Oracle Linux and Oracle VM installation media via Oracle Software Delivery Cloud. To stay current on errata updates, you might wish to subscribe to the Oracle Linux errata mailing list. This yum server is offered without support of any kind. If you require support, please consider purchasing Oracle Linux Support online or via your sales representative.
For this lab, we will replicate a local Oracle public yum server to speed up the switching process. The role of the local Oracle public yum server belongs to the ovm-mgr.oow.local (192.168.56.100) server.
#scp 192.168.56.100:/etc/yum.repos.d/myRepo.repo /etc/yum.repos.d/
Note: The root password requested from ovm-mgr.oow.local is ovsroot.
Figure 54. Preparing to copy the yum configuration.
redhat-release
package to oracle-release
by executing the following commands:
#yumdownloader oraclelinux-release.x86_64 oraclelinux-release-notes.x86_64
Figure 55. Passing the Oracle Linux release packages.
#rpm -Uhv --force oraclelinux-release*
Figure 56. Forcing the packages to upgrade.
#yum install oracle-logos.noarch oracle-rdbms-server-11gR2-preinstall.x86_64 oracleasm-support.x86_64
Note: This command will replace Red Hat logos, install the Unbreakable Enterprise Kernel (due to dependencies) and, last but not least, install Oracle software preinstallation packages such as the following:
oracle-rdbms-server-11GR2-preinstall
oracle-em-agent-12cR1-preinstall
These preinstallation packages are available for x86_64 only. Specifically, these packages do the following:
oracle
and the groups oinstall
and dba
, which are the defaults used during database installation/etc/sysctl.conf
to change settings for shared memory, semaphores, the maximum number of file descriptors, and so on/etc/security/limits.conf
, such as the number of open files, the number of processes, and the stack size to the minimum required based on the Oracle Database 11g Release 2 installation requirementsnuma=off
in the kernel boot parameters for an x86_64 machineThese packages automate and prepare Oracle Linux to accommodate software such as Oracle Database, Oracle WebLogic, Oracle Enterprise Manager Cloud Control, Oracle E-Business Suite, and so on.
Yum will ask for a confirmation to proceed with the install of packages; reply with Y:
Figure 57. Confirming the installation of the packages.
The installation process will complete in a few minutes as shown below:
Figure 58. Completion of package installation.
You can verify your GRUB configuration using the command cat /boot/grub/grub.conf
, for example:
Figure 59. Verifying the GRUB configuration.
In this example, "default kernel (1)" is the old Red Hat kernel; so we have to modify the default value to 0
. We would like also to see all boot steps, so, we need to remove rhgb quiet
from the boot kernel command line.
As root
, open the /boot/grub/grub.conf
file and change the default value from 1
to 0
and remove rhgb quiet
; to accomplish this task, you can use an editor such as vi or, if you don't know this tool, execute the following commands:
# sed -i s/default=1/default=0/ /boot/grub/grub.conf
# sed -i s/rhgb\ quiet// /boot/grub/grub.conf
After that, verify that the default value is correctly set (value is 0
).
#cat /boot/grub/grub.conf
Figure 60. Verifying that the default value is correct.
#chkconfig rhsmcertd off
# chkconfig rhnsd off
Figure 61. Expanding the pool.
Figure 62. Selecting the server.
Figure 63. Restarting the guest.
oracle-rdbms-server-11GR2-preinstall
:
ssh
.
#ssh root@<IP_address_of_guest>
Log in using the following:
Username: root
Password: ovsroot
In the following figure, the IP address of the guest is 192.168.56.254.
Figure 64. Connecting to the guest.
#uname -a
Figure 65. Verifying that the kernel loaded.
# cat /etc/sysctl.conf
Figure 66. Verifying the kernel parameters.
oracle
user introduced by the preinstallation package:
# cat /etc/security/limits.conf
Figure 67. Verifying the setting for the oracle
user.
By performing the steps in this section, we obtained the following fully supported and certified configuration for Oracle Database (whereas on VMware, Oracle Database was only supported, not certified):
Oracle VM => Oracle Linux => Oracle Database 11g Release 2
We obtained this fully certified Oracle Database configuration with a cheaper virtualization solution. You can obtain further details from the following My Oracle Support note:
"Support Position for Oracle Products Running on VMWare Virtualized Environments (Doc ID 249212.1)"
The first statement in the My Oracle Support note says "Oracle has not certified any of its products on VMware virtualized environments."
This section will describe how to build an Oracle VM Template starting from an existing guest (in our case, a guest created by a VMware OVA).
An Oracle VM Template is a reusable guest on which we will be able to create more guests automatically.
# yum install ovm*.
The main packages that will be installed are as follows:
ovm-template-config
: Oracle VM Template configuration toolovmd
: Oracle VM guest daemonlibovmapi
: Oracle VM APIs
Figure 68. Installing the RPMs.
The task will be completed in few seconds, and the result will be similar to Figure 69:
Figure 69. Result of installing the RPMs.
Once the console is open, execute the following commands:
# ovmd -s cleanup
# chkconfig ovmd on
# service ovmd enable-initial-config
# shutdown -h now
Note: If you aren't able to open a guest console and obtain a login prompt, connect via ssh
and execute all the steps in one command (the password is ovsroot
):
ssh root@<IP_address_obtained_earlier>
# ovmd -s cleanup; chkconfig ovmd on; service ovmd enable-initial-config; shutdown -h now
Note: If you are connected by ssh
, you'll lose the connection to the guest.
Figure 70. Preparing the guest.
Figure 71. Preparing to clone the guest.
Figure 72. Specifying that the guest be cloned.
Clone to a: Template
Clone Count: 1
Clone Name: Oracle Linux 6.4 - Oracle Database 11.2
Target Server Pool: ovm-pool.oow.local
Description: Oracle Linux Template with Oracle 11.2 Database on board
Click OK to confirm the creation of the new Oracle VM Template.
Figure 73. Cloning the guest to create a template.
Figure 74. Verifying the creation of the template.
Figure 75. Selecting the template.
Figure 76. Changing the template's OS.
Figure 77. Preparing to create a new guest.
Figure 78. Specifying the clone operation.
Clone to a: Virtual Machine
Clone Count: 1
Clone Name: vmdb02.oow.local
Target Server Pool: ovm-pool.oow.local
Description: clone pre-configured started from Oracle VM Template
Click OK to confirm the creation of the new Oracle VM guest.
Figure 79. Confirming the creation of the new guest.
Figure 80. Starting the guest.
Figure 81. Opening the guest's console.
Figure 82. Console options.
The Oracle VM Template configuration will ask for information for the new guest vmdb02.oow.local; enter the following details:
In the NETWORK category:
System host name: vmdb02.oow.local
Network device to configure: eth0
Activate interface on system boot: yes
Boot protocol: DHCP or static: static
IP address of the interface: 192.168.56.199
Netmask of the interface: 255.255.255.0
Gateway IP address: 192.168.56.1
DNS servers separated by comma: 192.168.56.1
In the AUTHENTICATION category:
System root password: <your_first_name>+<your_surname>+1
Note: Due to security policies, we have to insert one long password that contains at least one number.
Figure 83. Specifying the template's configuration.
ssh
.
Commands such as hostname
, ifconfig
, and uname -a
will show you details.
Figure 84. Connecting to the new guest.
Congratulations! You have successfully imported a guest from VMware to Oracle VM, switched from Red Hat to Oracle Linux, and created your first Oracle VM Template using Oracle VM Template configuration scripts.
You can now master your knowledge and create your own Oracle VM Template configuration scripts by following the guide deployed by Wim Coekaerts on his Oracle blog:
https://blogs.oracle.com/wim/entry/oracle_vm_template_config_script
This appendix explains how to prepare the environment if you want to run this lab from your home or office.
The first step is to find an x86 machine (server, desktop, or laptop) that has the required resources:
Then you download the required binaries, install Oracle VM VirtualBox on the machine, and install the following two servers (two Oracle VM VirtualBox virtual machines, in fact), as described in the next sections:
This section lists the required binaries and explains how to download them.
Java Runtime Environment (JRE) 7 (the javaws
binary is needed to get the VNC console)
Download the version for your OS from http://java.com/en/download/manual.jsp.
Oracle VM VirtualBox binaries (version 4.2.16 during writing of this document)
Download the version for your OS from https://www.virtualbox.org/wiki/Downloads.
File name:
For Oracle Linux or Red Hat Linux 6 (64 bits): VirtualBox-4.2-4.2.16_86992_el6-1.x86_64.rpm
(size 69 MB)
For Microsoft Windows: VirtualBox-4.2.16-86992-Win.exe
(size 95 MB)
Oracle VM VirtualBox Extension Pack 4.2.x
Download this from https://www.virtualbox.org/wiki/Downloads (the same file is used for all operating systems).
File name: Oracle_VM_VirtualBox_Extension_Pack-4.2.16-86992.vbox-extpack
(size 11 MB)
VirtualBox template for Oracle VM Server 3.2.4
Download this from http://www.oracle.com/virtualization/technologies/vm/downloads/template-downloads.html
File name: OracleVMServer.3.2.4-b525.ova
(size 249 MB)
VirtualBox template for Oracle VM Manager 3.2.4
Download this from http://www.oracle.com/virtualization/technologies/vm/downloads/template-downloads.html
File name: OracleVMManager.3.2.4-b524.ova
(size 2.75 GB)
IP address: 192.168.56.101
Netmask: 255.255.255.0
Gateway: 192.168.56.1
DNS server: 192.168.56.1 (we will not use DNS, but we have to give an IP address here)
Hostname: ovm-srv.oow.local
ssh
. If your machine runs Microsoft Windows, use PuTTY instead.
Note: The password is ovsroot.
$ ssh root@192.168.56.101
/etc/hosts
file:
192.168.56.100 ovm-mgr.oow.local ovm-mgr
192.168.56.101 ovm-srv.oow.local ovm-srv
192.168.56.199 vmdb02.oow.local vmdb02
In this lab, we create more than one guest and an Oracle VM Template starting from a Red Hat Enterprise Linux 6 guest exported from VMware.
The guest exported for this lab during Oracle OpenWorld was as follows:
There is more than one method for exporting a guest into OVA format. The method used in this lab is text mode using a tool named OVF Tool.
To export your own Red Hat Linux guest using OVF Tool, use syntax such as the following:
# ovftool /app/vmware/RH_Linux_6_x86-64/rhel_6_64-bit.vmx /app/rhel-64-oracle-rdbms.ova
You can put the .ova
file on the Oracle VM Manager server at the following path:
/var/www/html/ovas
For example:
scp /app/rhel-64-oracle-rdbms.ova 192.168.56.100:/var/www/html/ovas
Alternatively, you can put the .ova
file on your own web server; be sure to note the path where you put the file, because you will need this information during the lab.
Export methods using other VMware products are reported at these public links:
Note: If you are instead going to export a Microsoft Windows guest from VMware, you could encounter a known problem: the BSOD (blue screen of death) on the first run of your guest on Oracle VM. To sort out this problem, you have two options you can follow before exporting the guest:
.cab
files already present in the Microsoft Windows distribution.Reference: Oracle VM Windows PV Drivers for Microsoft Windows Guests (XP/Vista/7/2003/2008/2008 R2) 3.0.1 - 32-bit/64-bit (signed by Microsoft for the Windows Logo Program for Windows 2008, Windows 2008 R2, Windows 2003 and Windows 7)
IP address: 192.168.56.100
Netmask: 255.255.255.0
Gateway: 192.168.56.1
DNS server: 192.168.56.1 (we will not use DNS, but we have to give an IP address here)
Hostname: ovm-mgr.oow.local
ssh
. If your machine runs Microsoft Windows, use PuTTY instead.
Note: The password is ovsroot.
$ ssh root@192.168.56.100
/etc/hosts
file:
192.168.56.100 ovm-mgr.oow.local ovm-mgr
192.168.56.101 ovm-srv.oow.local ovm-srv
192.168.56.100 vmdb02.oow.local vmdb02
httpd
daemon on the manager (which will be used to upload templates):
# service httpd start
# chkconfig httpd on
httpd
daemon used for .ova
files and the yum server.
# mkdir -p /web/ovas
# mkdir -p /web/yum
# cd /var/www/html; ln -s /web/ovas .; ln -s /web/yum .
.ova
file you exported from VMware to the new directory created in the previous step. You should then obtain output similar to this if you list the contents of the directory:
[root@ovm-mgr]# ls -l
-rwxr-xr-x 1 ovmovm 9900220416 Aug 19 13:02 rhel-64-oracle-rdbms.ova
[root@ovm-mgr]# pwd
/web/ovas
# cd /etc/yum.repos.d
# wget https://public-yum.oracle.com/public-yum-el5.repo
# yum install yum-utils createrepo
# rm -f /etc/yum.repos.d/public-yum-el5.repo
# cd /etc/yum.repos.d
# wget https://public-yum.oracle.com/public-yum-ol6.repo
Note: It might take many hours, depending on your internet connection, because it will download about 27 GB; if you don't have much time, see the alternative option below.
# /usr/bin/reposync --repoid=ol6_latest --repoid=ol6_UEK_latest -repoid=ol6_addons -p /web/yum
# /usr/bin/createrepo /web/yum/ol6_latest/getPackage/
# /usr/bin/createrepo /web/yum/ol6_UEK_latest/getPackage/
# /usr/bin/createrepo /web/yum/ol6_addons/getPackage/
An alternative option is to directly use http://public-yum.oracle.com in this lab; to implement this alternative, you will need to have internet access and, at the same time, configure your Oracle VM Manager guest to reach external sites.
.repo
file to use on your future Oracle VM guest (with Oracle Linux 6 x86-64):
[local_ol6_latest]
name=Oracle Linux $releasever Latest ($basearch)
baseurl=http://192.168.56.100/yum/OracleLinux/OL6/latest/$basearch/
gpgkey=http://192.168.56.100/RPM-GPG-KEY-oracle-ol6
gpgcheck=0
enabled=1
[local_ol6_UEK_latest]
name=Latest Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch)
baseurl=http://192.168.56.100/yum/OracleLinux/OL6/UEK/latest/$basearch/
gpgkey=http://192.168.56.100/RPM-GPG-KEY-oracle-ol6
gpgcheck=0
enabled=1
#wget http://public-yum.oracle.com/repo/OracleLinux/OL5/9/base/x86_64/dhcp-3.0.5-31.el5_8.1.x86_64.rpm
# chkconfig dhcpd on
# service dhcpd start
Here is an example of a dhcpd.conf
file you can implement (/etc/dhcpd.conf
):
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
#
ddns-update-style interim;
ignore client-updates;
subnet 192.168.56.0 netmask 255.255.255.0 {
option routers 192.168.56.1;
option subnet-mask 255.255.255.0;
option nis-domain "oow.local";
option domain-name "oow.local";
option domain-name-servers 192.168.56.1;
range dynamic-bootp 192.168.56.250 192.168.56.254;
default-lease-time 86400;
max-lease-time 86400;
}
https://192.168.56.100:7002/ovm/console
.admin
and password Welcome1
.
You should now see the Oracle VM Manager console:
Figure 85. Oracle VM console.
You should now see the server, named ovm-srv.oow.local, under Unassigned Servers.
Oracle VM has a number of network channels: Server Management, Live Migrate, Cluster Heartbeat, Virtual Machine, and Storage. The Server Management, Live Migrate, and Cluster Heartbeat roles are automatically assigned to the management network when you discover Oracle VM Server.
For simplicity, we will use a single network for all roles by assigning the Virtual Machine and Storage roles to the default network.
Figure 86. Assigning roles to the default network.
The VNIC Manager creates VNICs, which can be used by virtual machines as network cards. You create virtual network interfaces by defining a range of MAC addresses to use for each VNIC.
You should now see those VNICs listed:
Figure 87. List of VNICs that were created.
Note: A server pool contains a group of Oracle VM servers, which as a group perform virtual machine management tasks, such as providing high availability (HA), implementing resource and power management policies, and providing access to networking, storage, and repositories.
The virtual machines running on a server can be "live migrated" to another server in the same pool. Of course, you need to have a shared storage system (NFS, iSCSI, or FC) between all the servers of the pool. The pool is called clustered in this case.
Here, for simplicity, we will create a non-clustered server pool with a single server and will use a local hard disk drive (HDD). (Actually, it is a file on the machine that is seen by Oracle VM VirtualBox as an HDD.)
Figure 88. Preparing to create a server pool.
Server pool name: ovm-pool.oow.local
Virtual IP address for the pool: 192.168.56.200
Note: The virtual IP address of the pool is assigned to one server in the pool, called the master server. Several actions are executed by this master server.
Figure 89. Creating the server pool.
Figure 90. The created server pool and server.
Before creating VMs hosted on the server pool, we need to create at least one storage repository in which to store the VMs' files.
Note: Only unused and unpartitioned local HDDs can be used.
Figure 91. Creating the storage repository.
Note: For non-NFS storage (which is our case here), an OCFS2 (Oracle Cluster File System 2) file system is created on the repository.
Figure 92. The newly created repository.
In addition, this hands-on-lab document is available at the following site: https://blogs.oracle.com/scoter/entry/oracle_openworld_2013_hands_on
Simon Coter is a technical expert in core technology for Oracle in Italy.
Special thanks to Christophe Pauliat, Olivier Canonge, and Doan Nguyen for their contributions.
Revision 1.0, 12/20/2013