In my previous posting I introduced the latest Oracle Real Application Cluster / Oracle VM template
. I mentioned how easy it is to deploy a complete Oracle RAC cluster with Oracle VM. In fact, you don't need any prior knowledge at all to get a complete production-ready setup going.
Here is an example... I built a 4 node RAC cluster, completely configured in just over 40 minutes - starting from import template into Oracle VM, create VMs to fully up and running Oracle RAC. And what was needed? 1 textfile with some hostnames and ip addresses and deploycluster.py.
The setup is a 4 node cluster where each VM has 8GB of RAM and 4 vCPUs. The shared ASM storage in this case is 100GB, 5 x 20GB volumes. The VM names are racovm.0-racovm.3. The deploycluster script starts the VMs, verifies the configuration and sends the database cluster configuration info through Oracle VM Manager to the 4 node VMs. Once the VMs are up and running, the first VM starts the actual Oracle RAC setup inside and talks to the 3 other VMs. I did not log into any VM until after everything was completed. In fact, I connected to the database remotely before logging in at all.
# ./deploycluster.py -u admin -H localhost --vms racovm.0,racovm.1,racovm.2,racovm.3 --netconfig ./netconfig.ini
Oracle RAC OneCommand (v1.1.0) for Oracle VM - deploy cluster - (c) 2011-2012 Oracle
(com: 26700:v1.1.0, lib: 126247:v1.1.0, var: 1100:v1.1.0) - v2.4.3 - wopr8.wimmekes.net
Invoked as root at Sat Jun 2 17:31:29 2012 (size: 37500, mtime: Wed May 16 00:13:19 2012)
Using: ./deploycluster.py -u admin -H localhost --vms racovm.0,racovm.1,racovm.2,racovm.3
INFO: Login password to Oracle VM Manager not supplied on command line or environment
INFO: Attempting to connect to Oracle VM Manager...
INFO: Oracle VM Client (184.108.40.2065) protocol (1.8) CONNECTED (tcp) to
Oracle VM Manager (220.127.116.116) protocol (1.8) IP (192.168.1.40)
INFO: Inspecting /root/rac/deploycluster/netconfig.ini for number of nodes defined...
INFO: Detected 4 nodes in: /root/rac/deploycluster/netconfig.ini
INFO: Located a total of (4) VMs;
4 VMs with a simple name of: ['racovm.0', 'racovm.1', 'racovm.2', 'racovm.3']
INFO: Verifying all (4) VMs are in Running state
INFO: VM with a simple name of "racovm.0" is in a Stopped state, attempting to start it...
INFO: VM with a simple name of "racovm.1" is in a Stopped state, attempting to start it...
INFO: VM with a simple name of "racovm.2" is in a Stopped state, attempting to start it...
INFO: VM with a simple name of "racovm.3" is in a Stopped state, attempting to start it...
INFO: Detected that all (4) VMs specified on command have (5) common shared disks between
INFO: The (4) VMs passed basic sanity checks and in Running state, sending cluster details
netconfig.ini (Network setup): /root/rac/deploycluster/netconfig.ini
INFO: Starting to send cluster details to all (4) VM(s).......
INFO: Sending to VM with a simple name of "racovm.0"....
INFO: Sending to VM with a simple name of "racovm.1".....
INFO: Sending to VM with a simple name of "racovm.2".....
INFO: Sending to VM with a simple name of "racovm.3"......
INFO: Cluster details sent to (4) VMs...
Check log (default location /u01/racovm/buildcluster.log) on build VM (racovm.0)...
INFO: deploycluster.py completed successfully at 17:32:02 in 33.2 seconds (00m:33s)
Logfile at: /root/rac/deploycluster/deploycluster2.log
# Node specific information
# Common data
# Device used to transfer network information to second node
# in interview mode
# 11gR2 specific data
last few lines of the in-VM log file :
2012-06-02 14:01:40:[clusterstate:Time :db11rac1] Completed successfully in 2 seconds
2012-06-02 14:01:40:[buildcluster:Done :db11rac1] Build 11gR2 RAC Cluster
2012-06-02 14:01:40:[buildcluster:Time :db11rac1] Completed successfully in 1779 seconds
From start_vm to completely configured : 29m:39s. The other 10m was the import template and create 4 VMs from template along with the shared storage configuration.
This consists of a complete Oracle 11gR2 RAC database with ASM, CRS and the RDBMS up and running on all 4 nodes. Simply connect and use. Production ready.
Oracle on Oracle.